Skip to content
TrustedSkillsbeta
Back to all skills

Dependency Scanning

Listed
bagelhole·vlatest·backend·MIT

Dependency Scanning identifies project dependencies, highlighting potential vulnerabilities and outdated versions for improved security & maintenance.

Repository

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 bagelhole/devops-security-agent-skills --skill dependency-scanning -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

bagelhole

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.

  • 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

    • security/scanning/dependency-scanning/SKILL.md:354remote script piped into a shell
      curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s

  • 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: github.com, 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

    github.comsource hostraw.githubusercontent.comsource host

  • 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.

  • Pinned to a commit: passed

    Scanned bagelhole/devops-security-agent-skills at 0365f57a07.

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

Commit
0365f57a07
Manifest
security/scanning/dependency-scanning/SKILL.md
Scanned
1 file, 401 lines
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 performs automated dependency scanning to identify known vulnerabilities in project dependencies. It analyzes a codebase or list of dependencies and reports any identified security risks based on publicly available vulnerability databases. The results help developers proactively address potential security issues before deployment.

When to use it

  • Before releasing new software: Scan dependencies to ensure no newly discovered vulnerabilities are introduced.
  • During code reviews: Integrate scanning into the review process for increased security awareness.
  • As part of CI/CD pipelines: Automate dependency checks within your continuous integration and delivery workflows.
  • Responding to security alerts: Quickly assess if a reported vulnerability affects your project's dependencies.

Key capabilities

  • Vulnerability identification from public databases
  • Dependency analysis
  • Reporting of identified vulnerabilities

Example prompts

  • "Scan the dependencies in this package.json file."
  • "Check for known vulnerabilities in my Python requirements."
  • “Analyze these project files and report any security risks.”

Tips & gotchas

The accuracy of the scan depends on the completeness and currency of the vulnerability databases used. Ensure your agent has access to up-to-date information for reliable results.