Repository navigation
fix(deps): clear the Scorecard vulnerability findings in the cli-tour lockfile - #20
Merged
Merged
Conversation
… lockfile Clears the advisories in Scorecard's Vulnerabilities finding by moving them out of the lockfile, with no change to a published range: no changeset, no release. Items: SEC11.
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.
Clears the Scorecard Vulnerabilities finding on examples (code scanning alert 5, SEC11). Its latest run, on 30403c4, lists 7 advisories, all in cli-tour's lockfile, which
npm auditthere reports the same way; Dependabot raised none of them because this repository's dependency graph lists no manifests. Nothing here is published, and cli-tour's package.json does not change.cli-tour: @cosyte/cli 0.1.1 to 0.1.3, inside its
^0.1.0range^1.32.2, so the lockfile moves the SDK from 1.29.0 to 1.32.2 (published 2026-10-23): GHSA-22jm-h49p-29qw, GHSA-46jr-4wx8-v453, GHSA-6qxp-vccf-f47h, GHSA-f897-62hf-6gxq (all high), GHSA-6prh-2h8m-c8cw and GHSA-rvq5-wwqv-78pq.npm updateoffered 4.13.17, which was published 2026-11-07, less than 24 hours before this change, and is not part of the fix, so its entry was restored; 4.13.16 satisfies both of its parents.npm auditis already clean.Checked: in cli-tour,
npm ciinstalls from the lockfile,npm lsreports no invalid or missing package,npm auditfinds 0 vulnerabilities, andnpm testpasses (8 of 8) on Node 26.Items: SEC11.