supply-chain-risk-auditor
Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-pa
v2026.11.12-149d7b23 instalaciones+3 en 7 días8,2 mil EstrellasCC-BY-SA-4.0sincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install trailofbits/supply-chain-risk-auditorEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquetee2509fde…05f8ec68
e2509fde06ec…3c0305f8ec6813 archivos · 66.1 KBEscaneoMedio21 hallazgos
- injection.no_confirmationSKILL.md:40
- Script ejecutable incluido con la skillscripts/collect.py
- injection.no_confirmationscripts/collect.py:282
Fuentegithub.com/trailofbits/skills/tree/main/plugins/supply-chain-risk-auditor/skills/supply-chain-risk-auditor@149d7b2
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
Generates a supply-chain risk report for a project's direct dependencies (npm, PyPI, Go), plus an advisory sweep of everything its lockfile resolves. Two deterministic scripts do the measuring; your job is the judgment they refuse to automate.
Why the scripts do the measuring, not you
Every figure in this report is a claim about somebody else's project, and hand-collected
figures were measured wrong before this skill was rebuilt around scripts: GitHub
contributor counts said five-plus people maintain lodash where npm's ACL says one, and
gh saw zero downloads for a package that moves 164 million a week. Do not estimate
maintainer counts, downloads, staleness, or CVE history from gh, web search, or
memory — run the collector, and quote what it measured.
The scripts enforce two rules worth knowing before you read their output:
- Unavailable data is never evidence of risk. Every criterion resolves to assessed-clean, assessed-flagged, or unassessable-with-a-reason.
- An absent measurement is never a clean verdict. A run that measured nothing exits non-zero instead of printing a report that finds nothing.
Workflow
Confirm the target directory has manifests:
package.json,pyproject.toml,requirements*.txt, orgo.mod. If none exist, say so and stop — do not audit an ecosystem this collector does not parse by hand. Lockfiles read for exact versions and the transitive sweep:package-lock.json/npm-shrinkwrap.json,uv.lock, and a go 1.17+go.mod.yarn.lock,pnpm-lock.yaml, andpoetry.lockare not read — the report says so when they are present, and versions fall back to pins or the latest release.Check
gh auth status. Unauthenticated GitHub allows 60 requests/hour against 5,000, and the collector makes several per dependency; expect repository criteria to come back unassessable without it. Say so rather than fixing it silently.Collect, then render. Put outputs somewhere outside the audited repository unless asked otherwise:
sh uv run {baseDir}/scripts/collect.py <project-dir> --json <out-dir>/findings.json uv run {baseDir}/scripts/render.py <out-dir>/findings.json --out <out-dir>/report.mdExpect a few minutes for ~50 dependencies — several HTTP requests per dependency, more with many Go modules, and slower without authenticated
gh. Ifcollect.pyexits non-zero, it is refusing to report — relay its message verbatim instead of retrying or working around it.Read
report.mdandfindings.json. The report is the deliverable; the JSON carries the datum behind every verdict when you need to cite one.Add what the collector cannot, clearly separated from what it measured:
- A short narrative for this reader: what to act on first, and why.
- Upgrade paths for advisory findings — check whether the fix is a patch or a major version away.
- Replacement candidates for abandoned or archived dependencies. Verify a candidate exists in the registry before naming it, and label these as judgment, not measurement.
- For flagged install scripts: whether
npm ci --ignore-scriptsis viable for this project's build.
Style for what you add
Write added prose the way a security report reads, and apply the same register to the report addendum and the final reply alike — replies get pasted into tickets and reports verbatim. State the finding, the datum behind it, and the action.
- Impersonal and declarative: no first or second person ("I ran the collector", "you should upgrade"), no contractions, no exclamation points.
- Active voice, with the subject matter as the actor: "upgrading to 1.19.0 clears all 25 advisories", not "it is recommended that axios be upgraded".
- Objective: no intensifiers or subjective framing ("very", "significant", "fortunately"), and no guesses about why the project chose what it chose.
- Tense: past for what the audit did, present for the state of the dependencies, future for the consequences of acting or not.
- Constructive: a recommendation names the action and its cost, never a culprit.
If the report-writing:writing-style skill is available in the session, follow it —
it is the full version of this register.
The rendered report carries facts only. The interpretive rules below are instructions to you, not content for the reader — do not copy them into the deliverable as caveats or framing.
Reading the report
- Unassessable is not risk. PyPI publishes no maintainer ACL and Go has no registry; those rows say what could not be known, not what is wrong.
- The coverage table bounds every claim. "No advisories" means "none among what was assessed" — check the assessed count before repeating a clean verdict.
- Quote figures verbatim. Do not re-derive, round, or embellish the report's numbers; every one is reproducible from the artifact.
- Absence from the findings is not endorsement. A dependency with no findings was measured against these criteria only.
Rationalizations to reject
- "
ghcan give me maintainer counts faster than the collector." Measured wrong — repo contributors and registry publish rights are different populations. - "No findings, so the dependencies are safe." Read the coverage table; on PyPI and Go, half the criteria are structurally unassessable.
- "The unassessable rows would just confuse the reader; I'll drop them." They are the boundary of every claim in the report. Dropping them turns partial coverage into a clean bill of health, which is the failure this skill was rebuilt to prevent.
- "The version is probably close enough." A range checked at latest-release and a lockfile-resolved version are different claims; the report labels which one it makes. Keep the label.
When not to use
- License compliance auditing.
- Scanning the target's own source for vulnerabilities or secrets — this skill never reads dependency source, only registry, advisory, and repository metadata.
- Judging whether the project installs or builds. The audit is designed to work from nothing more than the dependency list — manifests and lockfiles — and never installs, builds, or executes anything. Broken installs and import-time breakage are out of scope, and worth saying so if the user seems to expect them.
- Ecosystems other than npm, PyPI, and Go; say the ecosystem is unsupported rather than improvising an audit for it.
Archivos de esta versión
agents/1252 B
- openai.yaml252 B
assets/13.0 KB
- trail-of-bits-mark.svg3.0 KB
scripts/10214.4 KB
- collect.py64.2 KB
- model.py17.2 KB
- pyproject.toml683 B
- render.py34.4 KB
- sources.py28.5 KB
- test_collect.py37.2 KB
- test_model.py7.7 KB
- test_render.py14.0 KB
- test_sources.py10.3 KB
- uv.lock337 B
- SKILL.md6.8 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | Sí | Sí |
| Escribe archivos | Sí | Sí |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaPrompt injection · injection.no_confirmationSKILL.md:40
- MediaArchivo · Script ejecutable incluido con la skillscripts/collect.py
- MediaPrompt injection · injection.no_confirmationscripts/collect.py:282
- MediaPrompt injection · injection.no_confirmationscripts/collect.py:1103
- MediaArchivo · Script ejecutable incluido con la skillscripts/model.py
- MediaPrompt injection · injection.no_confirmationscripts/model.py:325
- MediaArchivo · Script ejecutable incluido con la skillscripts/render.py
- MediaPrompt injection · injection.no_confirmationscripts/render.py:116
- MediaPrompt injection · injection.no_confirmationscripts/render.py:179
- MediaPrompt injection · injection.no_confirmationscripts/render.py:512
- MediaPrompt injection · injection.no_confirmationscripts/render.py:608
- MediaArchivo · Script ejecutable incluido con la skillscripts/sources.py
- MediaPrompt injection · injection.no_confirmationscripts/sources.py:115
- MediaPrompt injection · injection.no_confirmationscripts/sources.py:287
- MediaArchivo · Script ejecutable incluido con la skillscripts/test_collect.py
- MediaPrompt injection · injection.no_confirmationscripts/test_collect.py:681
- MediaArchivo · Script ejecutable incluido con la skillscripts/test_model.py
- MediaArchivo · Script ejecutable incluido con la skillscripts/test_render.py
- MediaArchivo · Script ejecutable incluido con la skillscripts/test_sources.py
- MediaPrompt injection · injection.no_confirmationscripts/test_sources.py:177
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.11.12-149d7b2 | 13 nov 2026 | 149d7b2 | e2509fde | Firmada | – |
Más de trailofbits
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- 1337aeondave/13374
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login