Skip to content
TrustedSkillsbeta
Back to all skills

Dependency_Confusion_Test

Listed
charpup·vlatest·backend

Evaluates user input to detect potential dependency confusion attacks targeting package management systems.

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 charpup/skill-security-auditor --skill dependency_confusion_test -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

charpup

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 2 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

    SKILL.md has no YAML frontmatter, so it declares nothing machine-readable.

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

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.clawsec.io.

    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

    api.clawsec.ioundeclaredraw.githubusercontent.comsource hostgithub.comsource host

    What it found

    • config/default.yaml:24contacts api.clawsec.io
      feed_url: https://api.clawsec.io/v1/feed
    • lib/clawsec_integration.py:48contacts api.clawsec.io
      "https://api.clawsec.io/v1/feed"

  • 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 charpup/skill-security-auditor at 086718493c.

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

Commit
086718493c
Manifest
SKILL.md
Scanned
30 files, 3,341 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, dependency_confusion_test, assesses a project's vulnerability to dependency confusion attacks. It identifies potential conflicts arising from similarly named packages on different package registries (e.g., npm and GitHub). The tool helps determine if an attacker could trick the project into installing a malicious package instead of the intended one.

When to use it

  • Security Audits: Integrate this skill during security audits to proactively identify dependency confusion risks.
  • New Project Setup: Use before initial deployment to ensure dependencies are sourced from trusted registries.
  • Dependency Updates: Run after significant updates to project dependencies, as new versions can introduce vulnerabilities.
  • Supply Chain Risk Assessment: As part of a broader supply chain security assessment for software projects.

Key capabilities

  • Identifies potential dependency confusion conflicts.
  • Checks package names against multiple registries.
  • Provides reports on vulnerable dependencies.

Example prompts

  • "Test this project's dependencies for dependency confusion vulnerabilities."
  • "Analyze the package.json file at [project URL] for potential risks."
  • "Run a dependency confusion test and report any conflicts found."

Tips & gotchas

The skill requires access to the project’s package manifest (e.g., package.json, pom.xml). Ensure that the AI agent has appropriate permissions to read these files during execution.