[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757VGD5JNM4TC2DB3XXWKP6":3,"skill-same:01M757VGD5JNM4TC2DB3XXWKP6":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M757VGD5JNM4TC2DB3XXWKP6","dependency-audit",null,"Scan dependencies for known CVEs across ecosystems — npm audit, cargo audit, osv-scanner (multi-ecosystem, catches what npm audit misses), pip-audit. Triage by reachability (runtime vs dev) and severity before mass-bumping.","jpoindexter\u002FVanta","jpoindexter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2729617?v=4","01M72VRRYY1CP7RPF3B7GHH0CR","01M757GWDBT6RD147ZZ79N4MEX",4,"MIT","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fsecurity-skills\u002Fdependency-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: dependency-audit\ndescription: \"Scan dependencies for known CVEs across ecosystems — npm audit, cargo audit, osv-scanner (multi-ecosystem, catches what npm audit misses), pip-audit. Triage by reachability (runtime vs dev) and severity before mass-bumping.\"\ncreated: 2026-06-27\nupdated: 2026-06-27\ntags: [security, dependencies, cve, vulnerability, npm-audit, cargo-audit, osv-scanner, supply-chain]\n---\n\n# Dependency Audit\n\nMost of your attack surface is code you didn't write. This scan finds dependencies with **known** CVEs (the published ones — a database lookup, not analysis). The trap is reacting to the severity number alone: a 9.8 in a **dev-only test runner** is not a 9.8 in your shipped runtime. Triage by **reachability** first, severity second.\n\n## When to run\n\n- Before a release (a tagged version is what gets audited).\n- On a schedule (new CVEs land against deps you already shipped — yesterday's clean is today's stale).\n- After adding or bumping any dependency.\n\n## Run it — one ecosystem at a time, then the cross-cutting scanner\n\n```bash\n# Node \u002F TS — runtime only first (what you actually ship), then everything.\nnpm audit --omit=dev          # the deps that ship in `npm install --omit=dev`\nnpm audit                     # + dev\u002Fbuild tooling\n\n# Rust\ncargo audit                   # reads Cargo.lock against the RustSec advisory DB\n\n# Python\npip-audit                     # or: pip-audit -r requirements.txt\n\n# Multi-ecosystem, recursive — the thorough net. Catches lockfiles the per-tool\n# audits miss (sub-projects, docs sites) and flags dev deps explicitly.\nosv-scanner scan source --recursive .\n```\n\n`osv-scanner` is the most complete — it walks every lockfile in the tree (including a docs site or sub-package the per-ecosystem tools never see) and labels `(dev)` so you can triage by reachability.\n\n## Triage — reachability BEFORE severity\n\nFor each finding, ask in order:\n\n1. **Does it ship?** A `(dev)` dep (esbuild, vite, vitest, a linter) is NOT in your runtime if you install with `--omit=dev`. Real, but low urgency — it can't be hit by a user of the shipped artifact. Note it; don't panic-bump.\n2. **Is the vulnerable path reachable?** A CVE in a code path you never call is lower priority than a medium in your hot path.\n3. **THEN severity.** Among reachable, shipped deps, fix highest CVSS first.\n\n## Remediate — least-disruptive first\n\n1. **Patch bump** (`npm audit fix`, `cargo update -p \u003Ccrate>`) — safe, same major version. Do this freely.\n2. **Major bump** (vite 5→6, vitest 2→3) — a **breaking** change. Do it deliberately in its own branch with the full test suite green after, NEVER as a blind `audit fix --force` before a release.\n3. **Override \u002F pin** a transitive dep to a patched version (`overrides` in package.json, `[patch]` in Cargo) when the direct dep hasn't updated yet.\n4. **Accept with a note** when there's no fix and the dep is dev-only\u002Funreachable — record WHY in a `SECURITY.md` or an allowlist so the next audit doesn't re-litigate it. Silent acceptance reads as \"missed it.\"\n\n## The boundary\n\nThis finds **known, published** CVEs only — a zero-day or an unreported backdoor won't show. It's necessity, not sufficiency. Pair with `[[sast-scan]]` (your own code) and `[[secret-scan]]` (leaked credentials). Log what you deferred and why — see `[[security-preflight]]`.\n","# Dependency Audit\n\nMost of your attack surface is code you didn't write. This scan finds dependencies with **known** CVEs (the published ones — a database lookup, not analysis). The trap is reacting to the severity number alone: a 9.8 in a **dev-only test runner** is not a 9.8 in your shipped runtime. Triage by **reachability** first, severity second.\n\n## When to run\n\n- Before a release (a tagged version is what gets audited).\n- On a schedule (new CVEs land against deps you already shipped — yesterday's clean is today's stale).\n- After adding or bumping any dependency.\n\n## Run it — one ecosystem at a time, then the cross-cutting scanner\n\n```bash\n# Node \u002F TS — runtime only first (what you actually ship), then everything.\nnpm audit --omit=dev          # the deps that ship in `npm install --omit=dev`\nnpm audit                     # + dev\u002Fbuild tooling\n\n# Rust\ncargo audit                   # reads Cargo.lock against the RustSec advisory DB\n\n# Python\npip-audit                     # or: pip-audit -r requirements.txt\n\n# Multi-ecosystem, recursive — the thorough net. Catches lockfiles the per-tool\n# audits miss (sub-projects, docs sites) and flags dev deps explicitly.\nosv-scanner scan source --recursive .\n```\n\n`osv-scanner` is the most complete — it walks every lockfile in the tree (including a docs site or sub-package the per-ecosystem tools never see) and labels `(dev)` so you can triage by reachability.\n\n## Triage — reachability BEFORE severity\n\nFor each finding, ask in order:\n\n1. **Does it ship?** A `(dev)` dep (esbuild, vite, vitest, a linter) is NOT in your runtime if you install with `--omit=dev`. Real, but low urgency — it can't be hit by a user of the shipped artifact. Note it; don't panic-bump.\n2. **Is the vulnerable path reachable?** A CVE in a code path you never call is lower priority than a medium in your hot path.\n3. **THEN severity.** Among reachable, shipped deps, fix highest CVSS first.\n\n## Remediate — least-disruptive first\n\n1. **Patch bump** (`npm audit fix`, `cargo update -p \u003Ccrate>`) — safe, same major version. Do this freely.\n2. **Major bump** (vite 5→6, vitest 2→3) — a **breaking** change. Do it deliberately in its own branch with the full test suite green after, NEVER as a blind `audit fix --force` before a release.\n3. **Override \u002F pin** a transitive dep to a patched version (`overrides` in package.json, `[patch]` in Cargo) when the direct dep hasn't updated yet.\n4. **Accept with a note** when there's no fix and the dep is dev-only\u002Funreachable — record WHY in a `SECURITY.md` or an allowlist so the next audit doesn't re-litigate it. Silent acceptance reads as \"missed it.\"\n\n## The boundary\n\nThis finds **known, published** CVEs only — a zero-day or an unreported backdoor won't show. It's necessity, not sufficiency. Pair with `[[sast-scan]]` (your own code) and `[[secret-scan]]` (leaked credentials). Log what you deferred and why — see `[[security-preflight]]`.\n",{"name":5,"tags":23,"created":32,"updated":32,"description":7},[24,25,26,27,28,29,30,31],"security","dependencies","cve","vulnerability","npm-audit","cargo-audit","osv-scanner","supply-chain",1782518400000,"main","4911ae44bbb35beef4511ba298475ba5a82b7e1c","security-skills\u002Fdependency-audit",0,"https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta","https:\u002F\u002Fdocs.vanta.theft.studio","https:\u002F\u002Fgithub.com\u002Fjpoindexter","jason.theft.studio","Just some guy trying to build stuff","2026-11-12 17:11:35",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jpoindexter\u002FVanta --skill dependency-audit",{"tool":49,"command":50},"bunx","bunx skills add jpoindexter\u002FVanta --skill dependency-audit",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jpoindexter\u002FVanta --skill dependency-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fsecurity-skills\u002Fdependency-audit\u002FSKILL.md",true,[],[58,65,72,79,86,92],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7582PEM7XM8B98VFRDV0C0J","write-changelog","Turn a range of commits into a user-facing changelog","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fwrite-changelog\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7582KTQJMP5Y7GS83MS1C7Z","debug-flaky-test","Reproduce and isolate a flaky test before fixing it","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fdebug-flaky-test\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7582HG7XFM4Z5NGG1YFECT8","triage-incident","First 10 minutes of an incident — stabilize, then diagnose","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fhermes\u002Fskills\u002Ftriage-incident\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7582DQABK7A96XHMB770KQZ","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7582BBK8H0HGSXKK08FCXJ1","vanta-port-adapter","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fvanta-port-adapter\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M75828P8PX5XSBMJ2BVVDA9Y","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Ftest-driven-development\u002FSKILL.md",[],[]]