sec(frontend): pin npm dependencies to exact versions (closes #425)#872
sec(frontend): pin npm dependencies to exact versions (closes #425)#872cristim wants to merge 1 commit into
Conversation
Replace all 29 caret ranges (^) in package.json with the exact versions already recorded in package-lock.json. Exact pins eliminate the window where `npm install` (vs `npm ci`) resolves a newer minor/patch that may carry unaudited CVEs, and make supply-chain review straightforward. No functional change: every pinned version is the version currently installed, so the lockfile is unchanged.
|
@coderabbitai review |
|
Warning Review limit reached
More reviews will be available in 19 minutes and 53 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Actions performedReview triggered.
|
Summary
^) version ranges infrontend/package.jsonwith the exact versions already recorded inpackage-lock.json.npm install(rather thannpm ci) resolves a newer minor/patch release that may carry unaudited CVEs.Test plan
dependencies+devDependenciesentries verified to matchpackage-lock.jsonexactly (node script).npx tsc --noEmit-- no errors.npm test --coverage-- 65 suites, 2142 tests passed, 1 skipped.npm ciin a clean environment (disk full locally; CI will exercise this).