fix: bump dependencies and resolve npm audit vulnerabilities - #201
Merged
Conversation
Regenerate the stale package-lock.json and update dependencies so that `npm audit` reports 0 vulnerabilities (down from 51). Production: - axios ^1.15.0 -> ^1.18.1 (resolves multiple high-severity CVEs: SSRF, prototype pollution, ReDoS, credential leaks) - winston ^3.18.3 -> ^3.19.0 - @frontegg/entitlements-javascript-commons ^1.1.3 -> ^1.2.1 Overrides (transitive advisories): - form-data ^4.0.6 (CRLF injection; axios pulled vulnerable 4.0.5) - tmp ^0.2.5 -> ^0.2.7 (path traversal; 0.2.5 was still vulnerable) Dev: - express ^4.19.2 -> ^4.22.2 - jest-junit ^14.0.1 -> ^17.0.0 - semantic-release ^21.0.5 -> ^25.0.7 (drops bundled npm@9.9.4) Also add a Security section to the README documenting the patched dependency posture and responsible disclosure to security@frontegg.com. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Regenerates the stale
package-lock.jsonand bumps dependencies sonpm auditreports 0 vulnerabilities (down from 51). The stale lockfile (still pinning axios 1.15.0, express 4.21.2, and a bundlednpm@9.9.4) was the root cause of the inflated audit count.Changes
Production dependencies (shipped to consumers + the only tier the CI
audit-cigate enforces):axios^1.15.0→^1.18.1— resolves ~20 high-severity CVEs (SSRF, prototype pollution, ReDoS, credential leakage). The one production vulnerability.winston^3.18.3→^3.19.0@frontegg/entitlements-javascript-commons^1.1.3→^1.2.1Overrides (patch transitive advisories):
form-data^4.0.6— CRLF injection; axios pulled a vulnerable4.0.5tmp^0.2.5→^0.2.7— path traversal; the old^0.2.5override still resolved to vulnerable0.2.5(advisory requires ≥0.2.6)Dev dependencies (audit noise; not CI-gated since
audit-ci.jsonchasskip-dev: true, cleaned up for hygiene):express^4.19.2→^4.22.2jest-junit^14.0.1→^17.0.0semantic-release^21.0.5→^25.0.7— drops the bundlednpm@9.9.4that accounted for ~30 of the transitive advisoriesDocs:
docs/CHANGELOG.mdis intentionally untouched — it's auto-generated by semantic-release at release time.Verification
npm audit: 0 vulnerabilities (full tree and--omit=dev)tsc): ✅🤖 Generated with Claude Code