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.
fix: repo-wide security hardening from ZAP, Scorecard, and CodeQL audit #357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
fix: repo-wide security hardening from ZAP, Scorecard, and CodeQL audit #357
Changes from 4 commits
067c5cd612dbb0313741278424a730133a29ec17c50da78f800646f6File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Doesnpm install --no-save --ignore-scripts wrangler@3.114.17pin transitive dependencies or verify them against a repository-controlled checksum without a lockfile?💡 Result:
No.
wrangler@3.114.17pins only the top-level package version you asked for. Its transitive dependencies are still resolved at install time from whatever semver rangeswrangler(and its dependencies) declare, unless you use a lockfile (package-lock.json/npm-shrinkwrap.json) to freeze the full tree (includingresolved+integrityper package). [1][2]--no-savejust avoids writingwranglerinto yourpackage.json; it doesn’t by itself “pin” the transitive graph.--ignore-scriptsonly prevents lifecycle scripts from running. [1]Sources: npm install docs [1], package-lock format (including
integrity) [2], npm v5 integrity/cache notes [3], npm registry signature verification docs [4].wrangler@3.114.17is not reproducibly pinned—only the top-level version is fixed, while transitive dependencies are resolved at install time without a lockfile or repo-controlled checksums.--ignore-scriptsmitigates one supply-chain vector but does not achieve deterministic installation. Without a committedpackage-lock.json, the full dependency tree varies per run. Consider either checking in a lockfile for this isolated tool, or downloading and verifying a pre-built artifact before execution.🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.