Agent skill

Scan Dependencies

by whitphx in whitphx/stlite

CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use.

Apache-2.0Auto-check passed

Install Scan Dependencies

skills CLI
$ npx skills add whitphx/stlite --skill scan-dependencies -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install whitphx/stlite scan-dependencies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/whitphx/stlite.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/scan-dependencies .claude/skills/scan-dependencies && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scan-dependencies
GitHub stars
1.7k
Token cost
~1.7k tokens
SKILL.md length
574 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use.

  • Works in 4 steps: Construct the JSON Payload → Execute the Live Lookup → Decide an Action per Dependency → …
  • SKILL.md covers Description, Inputs and Execution Protocol
  • Calls jq and curl; reaches api.deps.dev

What it does

Scan Dependencies is an agent skill from whitphx/stlite. CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use. It MUST be called BEFORE any new package is imported or added to dependencies. It can also be used to check whether any new or existing dependencies are unsafe.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with WebAssembly. The repository describes itself as: Streamlit-Lite; In-browser Streamlit 🎈🚀. The licence is Apache-2.0.

Example prompts

  • “/scan-dependencies”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Construct the JSON Payload
  2. Execute the Live Lookup
  3. Decide an Action per Dependency
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 9a44ae8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.deps.dev

    Also links to:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scan Dependencies loads about 1.7k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from whitphx/stlite at commit 9a44ae8, republished under its Apache-2.0 licence (© whitphx). 574 words, ~1,727 tokens.

Download SKILL.mdSave it as .claude/skills/scan-dependencies/SKILL.md (or your agent's skills folder).
name
scan-dependencies
description
CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use. It MUST be called BEFORE any new package is imported or added to dependencies. It can also be used to check whether any new or existing dependencies are unsafe.

Skill: Evaluate Dependency Security via deps.dev Findings API

Adapted from the deps.dev example skill (Apache License 2.0), with a complete lookup script and an explicit finding-to-action policy based on the v3alpha API definition.

Description

This skill automates the process of auditing package dependencies before adoption. By querying the Open Source Insights (deps.dev) API, it checks a batch of package versions for active security findings (advisories and vulnerabilities) and outputs a clear action plan (ALLOW, CAUTION, or BLOCK).

Inputs

An array of target dependencies. Each dependency must contain:

  • system: The ecosystem name. Must be uppercase: NPM, PYPI, MAVEN, GO, CARGO, NUGET, or RUBYGEMS.
  • name: The canonical name of the package (e.g., org.apache.logging.log4j:log4j-core for Maven, or normalized lowercase for PyPI/NuGet).
  • version: The explicit version string to audit. This may be unset.

Only set the version field if you know the exact version of the package. This field should not be set if only a version range is known (for example, ^1.0.0 is not acceptable).


Execution Protocol

Step 1: Construct the JSON Payload

Map the incoming dependency list into a single JSON batch request object. Ensure all items are nested inside the "requests" array under a "versionKey" or "packageKey" parameter.

Payload Schema Example:

json
{
  "requests": [
    {
      "versionKey": {
        "system": "NPM",
        "name": "express",
        "version": "4.17.1"
      }
    },
    {
      "packageKey": {
        "system": "PYPI",
        "name": "requests"
      }
    }
  ]
}
Step 2: Execute the Live Lookup

Write the payload built in Step 1 from the actual input list (not the example above) to a file, then POST it. Follow nextPageToken until it is absent so the result set is complete. -f makes HTTP errors fail the command instead of returning an error body.

bash
echo "Scanning dependencies for safety..."
# deps-request.json holds the Step 1 payload, e.g. built with jq:
#   jq -n '{requests: [{versionKey: {system: "NPM", name: "express", version: "4.17.1"}}]}' > deps-request.json
rm -f deps-findings-*.json
page_token=""
page=0
while :; do
  page=$((page + 1))
  jq --arg t "$page_token" 'if $t == "" then . else . + {pageToken: $t} end' \
    deps-request.json > "deps-request-page.json" || exit 1
  curl -fsS -X POST https://api.deps.dev/v3alpha/findingsbatch \
    -H 'Content-Type: application/json' \
    --data-binary @deps-request-page.json \
    -o "deps-findings-$page.json" || { echo "Lookup failed: unknown risk"; exit 1; }
  jq -e . "deps-findings-$page.json" > /dev/null || { echo "Invalid JSON: unknown risk"; exit 1; }
  page_token="$(jq -r '.nextPageToken // ""' "deps-findings-$page.json")"
  [ -z "$page_token" ] && break
done
jq -s '[.[].responses[]?]' deps-findings-*.json > deps-findings.json

If the request fails, returns invalid JSON, or pagination cannot be completed, the scan result is unknown risk for every dependency in the batch. Report that to the user before proceeding; do not treat it as ALLOW.

Show full SKILL.md (284 more words)Show less
Step 3: Decide an Action per Dependency

Match each input dependency to its entry in responses[] (the request field echoes the request as sent, before canonicalization). A dependency with no matching response, or a response without findings, is unknown risk and gets CAUTION.

Collect the findings that apply to it:

  • findings.packageFindings[] (package-scoped; apply to every version).
  • For a versionKey request: findings.requestedVersion.findings[].
  • For a packageKey request: findings.defaultVersion.findings[] (the version that would be installed without an explicit version).

Each finding has a type and a risk. Choose the most severe action:

ActionWhen
BLOCKAny finding with type: MALICIOUS, or any finding with risk: RISK_CRITICAL.
CAUTIONAny other finding whose type is not REMEDIATION (e.g. VULNERABLE, DEPRECATED, LOW_USAGE, COOLDOWN, NOT_FOUND, or an unrecognized type), whatever its risk; any REMEDIATION finding with risk: RISK_HIGH, RISK_MEDIUM, or an unrecognized risk (including RISK_UNSPECIFIED); or missing/incomplete results.
ALLOWNo findings at all, or only REMEDIATION findings with risk: RISK_LOW or RISK_INFORMATIONAL.

Notes:

  • COOLDOWN means the version is newer than the deps.dev cooldown. Pick an older version or wait; never bypass the project's own cooldowns (package manager age gates, Dependabot cooldowns) to adopt it.
  • findings.recommendedVersions[] lists lower-risk versions; suggest one when the result is BLOCK or CAUTION.
Step 4: Report

Output one line per dependency with its action and the findings (type, risk, and any deprecatedContext.reason or lowUsageContext.alternativePackages) that drove it. Do not proceed on BLOCK; surface CAUTION to the user before proceeding.

Note that just because a dependency doesn't show up in this list, that doesn't mean we are 100% sure that it is safe. CRITICAL: Treat unflagged dependencies as having unknown risk levels. You must state clearly that the scanner only detects known issues and cannot guarantee absolute security.

© whitphx, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/scan-dependencies of whitphx/stlite.

Open the folder on GitHubat commit 9a44ae8

Compare with similar skills

Scan Dependencies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scan Dependencies compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scan Dependencies this skillwhitphx/stlite1.7k—~1.7kAutomated safety check: PassApache-2.0
RuView CLI, API and WASMruvnet/RuView97k—~1.2kAutomated safety check: NotesMIT
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0
Update V86felixrieseberg/windows9524k—~1.7kAutomated safety check: PassCustom licence
Dotlottie WebLottieFiles/dotlottie-web892—~3.5kAutomated safety check: PassMIT
Adding Internal API RouteTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

    97k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Update V86

    felixrieseberg/windows95

    Build and install v86 (wasm + libv86.js + BIOS) into windows95.

    24k GitHub stars~1.7k tokensUpdated 27 days ago
    Testing & QAAuto-check passed
  • Dotlottie Web

    LottieFiles/dotlottie-web

    Implement Lottie animations using dotLottie runtimes (@lottiefiles/dotlottie-web and @lottiefiles/dotlottie-react).

    892 GitHub stars~3.5k tokensUpdated yesterday
    Media & CreativeAuto-check passed
  • Adding Internal API Route

    TriliumNext/Trilium

    A skill your agent uses when adding, moving, or wiring an internal REST endpoint in Trilium (a new /api/ route) — choosing between a core-shared handler (packages/trilium-core/src/routes/index.ts…

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Client Request Signature Reversal

    awarexone/Agentic-Bug-Hunter

    Recovers a client-side request signature or anti-bot token just far enough to replay blocked requests in bug bounty testing, starting from a captured packet.

    5.3k GitHub stars~4.7k tokensUpdated 3 days ago
    SecurityAuto-check passed

More from whitphx/stlite

  • Changeset

    whitphx/stlite

    Create or update a changeset fragment (.changeset/.md) reflecting the changes made in the current session or branch.

    1.7k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Streamlit Rebase

    whitphx/stlite

    Rebase our custom fork of the Streamlit repository onto new upstream Streamlit release

    1.7k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Copy Samples

    whitphx/stlite

    Update sharing-editor sample apps from the streamlit/docs repository

    1.7k GitHub stars~393 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Scan Dependencies

What does Scan Dependencies do?

CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use. Scan Dependencies is an agent skill from whitphx/stlite. CRITICAL: The scan-dependencies skill flags any dependencies that are unsafe to use.

How do I install Scan Dependencies in Claude Code?

Run `npx skills add whitphx/stlite --skill scan-dependencies -a claude-code`. Or copy the skill folder (.claude/skills/scan-dependencies in whitphx/stlite) into .claude/skills/scan-dependencies in your project. Claude Code loads it when a task matches its description.

How do I install Scan Dependencies in Codex?

Run `npx skills add whitphx/stlite --skill scan-dependencies -a codex`. Or copy the skill folder (.claude/skills/scan-dependencies in whitphx/stlite) into .agents/skills/scan-dependencies in your project. Codex loads it when a task matches its description.

Can I use Scan Dependencies in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add whitphx/stlite --skill scan-dependencies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scan-dependencies, .gemini/skills/scan-dependencies, .github/skills/scan-dependencies and .opencode/skills/scan-dependencies in your project.

What does Scan Dependencies need to run?

Going by SKILL.md and its folder, Scan Dependencies needs the command-line tools its instructions call (jq and curl).

Does Scan Dependencies access the network?

SKILL.md names 2 domains. In commands or code: api.deps.dev; the agent is likely to contact it when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Scan Dependencies safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scan Dependencies use?

Scan Dependencies is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scan Dependencies use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scan Dependencies?

Skills that share tags, products or a category with Scan Dependencies: RuView CLI, API and WASM (ruvnet/RuView, 97k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), Update V86 (felixrieseberg/windows95, 24k stars) and Dotlottie Web (LottieFiles/dotlottie-web, 892 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scan Dependencies?

whitphx (a GitHub user) maintains it in whitphx/stlite, which has 1,669 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: whitphx/stlite on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.