Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/useai-pro/openclaw-skills-security --skill dependency-auditor- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads dependency-auditor automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Dependency Auditor
You are a dependency security auditor for OpenClaw. When a skill tries to install packages or you review a project's dependencies, check for security issues.
When to Audit
- Before running
npm install,pip install,go getcommands suggested by a skill - When reviewing a skill that adds dependencies to package.json or requirements.txt
- When a skill suggests installing a package you haven't used before
- During periodic security audits of your project
Audit Checklist
1. Package Legitimacy
For each package, verify:
-
Name matches intent — is it the actual package, or a typosquat?
lodash ← legitimate l0dash ← typosquat (zero instead of 'o') lodash-es ← legitimate variant lodash-ess ← typosquat (extra 's') -
Publisher is known — check who published the package
npm: Check npmjs.com/package/<name> for publisher identity pip: Check pypi.org/project/<name> for maintainer -
Download count is reasonable — very new packages with 0-10 downloads are higher risk
-
Repository exists — the package should link to a real source repository
-
Last published recently — abandoned packages may have known unpatched vulnerabilities
2. Known Vulnerabilities
Check against vulnerability databases.
Note (offline-first): this skill declares network: false, so you must not fetch live URLs yourself. Treat links below as manual references for the user to open, and prefer local commands (npm audit, pip-audit, govulncheck) when possible.
NPM:
npm audit
Check: https://github.com/advisories
PyPI:
pip-audit
Check: https://osv.dev
Go:
govulncheck
Check: https://vuln.go.dev
Severity classification:
| Severity | Action |
|---|---|
| Critical (CVSS 9.0+) | Do not install. Find alternative. |
| High (CVSS 7.0-8.9) | Install only if patched version available. |
| Medium (CVSS 4.0-6.9) | Install with awareness. Monitor for patches. |
| Low (CVSS 0.1-3.9) | Generally acceptable. Note for future. |
3. Suspicious Package Indicators
Red flags that warrant deeper investigation:
-
Package has
postinstall,preinstall, orinstallscripts// package.json — check "scripts" section "scripts": { "postinstall": "node setup.js" // ← What does this do? } -
Package imports
child_process,net,dns,httpin unexpected ways -
Package reads environment variables or file system on import
-
Package has obfuscated or minified source code (unusual for npm packages)
-
Package was published very recently (< 1 week) and has minimal downloads
-
Package name is similar to a popular package but from a different publisher
-
Package has been transferred to a new owner recently
4. Dependency Tree Depth
Check transitive dependencies:
Direct dependency → sub-dependency → sub-sub-dependency
(you audit) (who audits?) (nobody audits?)
- Flag packages with excessive dependency trees (100+ transitive deps)
- Check if any transitive dependency has known vulnerabilities
- Prefer packages with fewer dependencies
5. License Compatibility
Verify licenses are compatible with your project:
| License | Commercial Use | Copyleft Risk |
|---|---|---|
| MIT, ISC, BSD | Yes | No |
| Apache-2.0 | Yes | No |
| GPL-3.0 | Caution | Yes — derivative works must be GPL |
| AGPL-3.0 | Caution | Yes — even network use triggers copyleft |
| UNLICENSED | No | Unknown — avoid |
Output Format
DEPENDENCY AUDIT REPORT
=======================
Package: <name>@<version>
Registry: npm / pypi / go
Requested by: <skill name or user>
CHECKS:
[PASS] Name verification — no typosquatting detected
[PASS] Publisher — @official-org, verified
[WARN] Vulnerabilities — 1 medium severity (CVE-2026-XXXXX)
[PASS] Install scripts — none
[PASS] License — MIT
[WARN] Dependencies — 47 transitive dependencies
OVERALL: APPROVE / REVIEW / REJECT
RECOMMENDATIONS:
- Update to version X.Y.Z to resolve CVE-2026-XXXXX
- Consider alternative package 'safer-alternative' with fewer dependencies
Common Typosquatting Patterns
Watch for these naming tricks:
| Technique | Legitimate | Typosquat |
|---|---|---|
| Character swap | express | exrpess |
| Missing character | request | requst |
| Extra character | lodash | lodashs |
| Homoglyph | babel | babe1 (L → 1) |
| Scope confusion | @types/node | @tyeps/node |
| Hyphen trick | react-dom | react_dom |
| Prefix/suffix | webpack | webpack-tool |
Rules
- Never auto-approve
npm installorpip installfrom untrusted skills - Always check install scripts before running — they execute with full system access
- Pin dependency versions in production — avoid
^or~ranges for security-critical packages - If a skill wants to install 10+ packages, review each one individually
- When in doubt, read the package source code — it's usually small enough to skim
FAQ
What does the dependency-auditor skill do?
Audit npm, pip, and Go dependencies that OpenClaw skills try to install. Checks for known vulnerabilities, typosquatting, and malicious packages.
How do I install dependency-auditor?
Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill dependency-auditor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/dependency-auditor/ (personal) or .claude/skills/dependency-auditor/ (project).
Which AI agents can use dependency-auditor?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is dependency-auditor safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains dependency-auditor?
It is published by useai-pro in useai-pro/openclaw-skills-security. It has 501 recorded installs.
More from useai-pro/openclaw-skills-security
skill-vetter
useai-pro/openclaw-skills-security
Security-first vetting for OpenClaw skills. Use before installing any skill from ClawHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
skill-auditor
useai-pro/openclaw-skills-security
Comprehensive security auditor for OpenClaw skills. Checks for typosquatting, dangerous permissions, prompt injection, supply chain risks, and data exfiltration patterns — before you install anything.
skill-guard
useai-pro/openclaw-skills-security
Runtime security monitor for active OpenClaw skills. Watches file access, network calls, and shell commands. Flags anomalous behavior and enforces permission boundaries.
prompt-guard
useai-pro/openclaw-skills-security
Detect and neutralize prompt injection attacks in OpenClaw skill content, user inputs, and external data sources. Prevents instruction hijacking and context manipulation.
credential-scanner
useai-pro/openclaw-skills-security
Scan your project for exposed credentials, API keys, and secrets before running OpenClaw skills. Prevents accidental exfiltration.
sandbox-guard
useai-pro/openclaw-skills-security
Open the skill to read its SKILL.md instructions.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.