Repository navigation
ci: add an optional npm dependency report - #1007
Open
PresentJay wants to merge 1 commit into
Open
PresentJay wants to merge 1 commit into
PresentJay wants to merge 1 commit into
Conversation
|
Author
|
I contribute to zero-shelter and proposed this as an optional snapshot of the committed npm advisories, alongside mountebank's CircleCI and CodeQL checks. Would a manually requested HTML artifact fit your dependency review process? If the current tooling already gives you this view, I am happy to withdraw the proposal. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



mountebank already has CodeQL and a CircleCI application pipeline. I contribute to zero-shelter and proposed this as an experiment with a manual advisory snapshot of the committed npm tree, without starting the test-double server.
Only
.github/workflows/dependency-report.ymlchanges. Theworkflow_dispatchjob usescontents: read, SHA-pinned official actions and pinnedzero-shelter@0.0.10. It readsnpm audit --package-lock-only --ignore-scriptsoutput and retains generated HTML for 7 days. Findings exit1; scanner/judgement errors exit2; both fail the job. The job installs no project dependencies, runs no project lifecycle scripts, accepts no baseline and changes no CircleCI or release setting.The saved local validation at
80a3525c531fproduced 35 raw / 29 merged / 29 outstanding findings, 0 accepted. npm audit and JSON/HTML exited1. This reduction occurred within one npm audit input; it is not evidence of cross-scanner reconciliation. YAML, Bash and whitespace checks passed; manifest and lockfile stayed unchanged. These are earlier results, not a new scan. The application/OS test matrix and new hosted manual workflow were not run locally.The report does not establish reachability. npm audit sends dependency metadata to the configured registry, and npx downloads and executes the third-party CLI in CI. I used AI assistance to prepare this proposal and description.
Would this report add a useful review step alongside CircleCI? I'm happy to withdraw it if it duplicates the existing process.