Skip to content

ci: add an opt-in npm dependency report - #400

Closed
PresentJay wants to merge 1 commit into
versatica:v3from
PresentJay:ci/zero-shelter-report-20261103-b
Closed

PresentJay wants to merge 1 commit into
versatica:v3from
PresentJay:ci/zero-shelter-report-20261103-b

Conversation

@PresentJay

Copy link
Copy Markdown

Why this helps

mediasoup-client.yaml already gates CI with npm audit --omit dev across OS/Node22/24/26. It does not produce a full dev-inclusive ranked HTML report. 9 runtime and15 dev direct dependencies.

Supplement the production audit with opt-in developer-toolchain triage; preserve the production audit exit status and all release chains.

Change

Adds a separate manual-only Dependency triage report workflow. Maintainers can request a ranked HTML snapshot from the Actions tab. The workflow reads the committed npm lock using npm audit --package-lock-only --ignore-scripts, then feeds the completed JSON into pinned zero-shelter@0.0.10. It uploads the HTML for seven days and requests only contents: read.

Existing validation, security and publishing workflows stay intact. Findings retain exit 1; scanner/judgement errors retain exit 2. The report therefore cannot turn a failed scan into a clean result or accept existing findings into a baseline. There is no automatic schedule or new pull-request gate.

Observed validation

  • Upstream base: 2892e7a556c3 (v3).
  • Active lockfile consumer: mediasoup-client.yaml uses npm ci; npm publishing workflow also uses npm ci --ignore-scripts --foreground-scripts.
  • In this checkout, completed npm input produced 3 raw / 3 merged / 3 outstanding / 0 accepted findings. npm audit exited 1; the published CLI returned 1 for JSON and 1 for HTML.
  • A synthetic failed-scanner JSON returned 2.
  • The workflow parses as YAML; both shell blocks pass bash -n; git diff --check passes. Manifest and lockfile SHA-256 hashes match before and after the scan.

Unverified: the hosted Actions run and the existing application test/build matrix. This change adds one workflow only and was tested against the actual committed lockfile without installing the application. The report covers npm dependency advisories; it does not establish exploitability, reachability or complete project security. Target existing default v3 branch; do not assume main. Do not invoke npm run release or alter release/website/demo automation.

Network/data: npm audit queries the configured npm advisory service, and npx downloads the pinned public CLI. The artifact contains dependency report metadata; no account/API secrets or application data are needed.

Disclosure

I contribute to zero-shelter. This implementation, validation and PR description were prepared with AI assistance. This is an optional maintainer-tooling proposal; no dependency upgrade or risk acceptance is included.

@ibc

ibc commented Nov 2, 2026

Copy link
Copy Markdown
Member

Thanks but we don't need this and I don't want to introduce more CI stuff.

@ibc ibc closed this Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants