Ghost Scan Deps
ListedThis tool scans project dependencies for vulnerable or outdated packages, helping developers proactively identify and mitigate security risks.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add ghostsecurity/skills --skill ghost-scan-deps -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
ghostsecurity
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.
Automated safety checks
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.
No pipe-to-shell installers: failed
Runs code fetched at install time in 1 place.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found
- plugins/ghost/skills/scan-deps/agents/init/agent.md:16remote script piped into a shell
curl -sfL https://raw.githubusercontent.com/ghostsecurity/wraith/main/scripts/install.sh | bash
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Only contacts known or declared hosts: raw.githubusercontent.com.
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.
Hosts contacted
raw.githubusercontent.comsource hostNo 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.
Pinned to a commit: passed
Scanned ghostsecurity/skills at 6ea8e3ba66.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6ea8e3ba66
- Scanned
- 10 files, 1,831 lines
About this skill
What it does
This skill, Ghost Scan Deps, performs Software Composition Analysis (SCA) scanning of project dependencies to identify vulnerable or outdated packages. It orchestrates a series of sub-agents to automate this process, including initializing a tool called Wraith, discovering dependency lockfiles within the repository, and generating a final scan report detailing potential security risks. The skill focuses on identifying exploitable vulnerabilities in project dependencies.
When to use it
- When onboarding a new project and needing an initial security assessment of its dependencies.
- As part of a continuous integration/continuous delivery (CI/CD) pipeline to proactively identify vulnerabilities during development.
- During code reviews to ensure developers are aware of potential dependency-related risks.
- To quickly assess the security posture of existing projects with known or suspected dependency issues.
Key capabilities
- Wraith Initialization: Installs and configures the Wraith binary for vulnerability scanning.
- Lockfile Discovery: Automatically identifies all relevant dependency lockfiles (e.g.,
go.mod,package-lock.json). - Vulnerability Scanning: Runs Wraith against each discovered lockfile to identify known vulnerabilities.
- Exploitability Assessment: Analyzes identified candidates to determine their exploitability.
- Report Generation: Creates a summary report detailing the scan findings.
Example prompts
- "Run a security scan on this project."
- "Scan dependencies for known vulnerabilities and provide a detailed report."
- "Perform an SCA scan of the repository at the current working directory."
Tips & gotchas
- The skill requires Git to determine short commit hashes; if run outside of a Git repository, it falls back to using the date as a substitute.
- The initial setup step involves computing and storing several variables (scan_dir, cache_dir, skill_dir) which are essential for subsequent steps. Ensure these values are correctly stored and available to the agent.
- This skill is an orchestrator; it relies on sub-agents and does not perform any of the core scanning work itself.