Skip to content
TrustedSkillsbeta
Back to all skills

Codebase Cleanup Deps Audit

Listed
sickn33·vlatest·backend·MIT

Identifies outdated, unused, or vulnerable dependencies within a codebase for improved security and maintainability.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill codebase-cleanup-deps-audit -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sickn33

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
0 files
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps AI agents identify and remove unused or outdated dependencies within a codebase. It performs an audit to ensure the project's package management files reflect only necessary libraries, reducing bloat and potential security risks.

When to use it

  • Before deploying a production build to minimize attack surface and bundle size.
  • During refactoring phases to eliminate legacy packages no longer in use.
  • When troubleshooting dependency conflicts or "dependency hell" scenarios.
  • To maintain compliance with license requirements for open-source components.

Key capabilities

  • Scans codebase files to detect referenced libraries.
  • Compares actual usage against package.json, requirements.txt, or equivalent manifest files.
  • Identifies orphaned dependencies that are declared but never imported.
  • Flags outdated versions of critical security packages.

Example prompts

  • "Audit my Python project for unused dependencies and list them."
  • "Check if the latest version of React is installed and flag any outdated packages in my Node.js app."
  • "Generate a report of all third-party libraries currently in use versus those declared but unused."

Tips & gotchas

Ensure your codebase is up to date before running an audit, as stale imports might be flagged incorrectly if the project hasn't been committed recently. Always review the generated list manually before deleting packages to avoid breaking features that rely on implicit or dynamic imports not caught by static analysis.