> For the complete documentation index, see [llms.txt](https://docs.thecolliery.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thecolliery.org/tools/canaries/skill-6.md).

# supply-chain-audit

Software supply chain audit — dependencies (CVEs, maintenance, licenses, transitive risk), build/CI integrity (SHA-pinned actions, lockfile, CI-only release), artifact integrity (checksums, signing, S

Audit what the project trusts: deps, build pipeline, shipped artifact. Report; do NOT change deps unless asked.

## 1. Dependencies

* **Scope** — honor `.coalmine.json` `packageManifests` if set: scan exactly those manifest/lockfile paths; else infer by inspecting the repo.
* **CVEs** — run ecosystem auditor; cross-check every hit in GHSA/OSV/NVD. Cite advisory ID + affected range + fixed version. (Invoke source-grounding — never from memory.)
* **Maintenance** — last release, commit recency, bus-factor, archived/deprecated flag.
* **License** — flag copyleft inside permissive project, missing/unknown license.
* **Transitive** — full tree; name the parent to bump for a transitive fix.
* **Behavior** — phone home? install scripts? unexpected egress?

## 2. Build / CI

* CI-only release builds?
* Actions pinned to commit SHA (not floating tag)?
* Lockfile committed + enforced in CI?
* Minimal token scope? No `pull_request_target`?

## 3. Artifact

* SHA-256 checksums published for every binary?
* Signed (Authenticode/GPG)? Gap documented honestly?
* SBOM generated?
* User can verify before running?

## Tooling

Per-ecosystem vuln/license/outdated commands + offline fallback: read `references/tooling.md` when selecting scanners.

## Discipline

* Ground every CVE/fixed-version in an advisory. Never from memory.
* Don't auto-change deps — report + recommend; user decides (bumps break builds).
* State what was NOT scanned. Blocked network scans → lockfile inspection fallback (see `references/tooling.md`), mark live checks N-A.

## Fix mode (choice-gated)

After the report, present via `ask_question`:

* **Pin safe now** — commit already-present unchanged lockfile, pin CI action to current SHA, add missing checksum step. Each: checkpoint → apply → verify.
* **Let me pick** — user-selected fixes only.
* **Report only** — change nothing.

NEVER auto-fix: dep version bump, lockfile regen (re-resolves entire transitive tree).

## Grants & denials (CLASSIFY-BLOCK)

| class   | step it powers                                           | grant                                                     | on denial                                                                                  |
| ------- | -------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| read    | scan manifests/lockfiles; run the ecosystem auditor      | `Read`·`Grep`·`Glob`·`Bash` (read-only)                   | refuse that manifest, name it in "Not scanned" — never a clean bill                        |
| write   | Fix mode's pin/commit, incl. checkpoint → apply → verify | `Edit`·`Write`·`Bash` (checkpoint/verify need exec)       | report the pin as NOT applied AND the checkpoint/verify as NOT available, never claim done |
| network | GHSA/OSV/NVD cross-check                                 | `WebSearch`·`WebFetch` (or delegated to source-grounding) | `⚠️ unverified: check [advisory ID]`                                                       |

## Output

`| package | direct/transitive | issue | severity | advisory | fixed-in | action |` Build+artifact checklist · Summary (counts + top fixes) · Not scanned

For `ReportFindings`: `file` = the manifest/lockfile path that named the package (`packageManifests`, or the inferred one); `line` is best-effort (the pin/version line if easily found) or omitted and named imprecise per the shared reporting rail — never fabricate a line.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thecolliery.org/tools/canaries/skill-6.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.