fix: remove tracked node_modules, add SECURITY.md#26
Merged
Conversation
- Remove 186 packages (23MB) of node_modules that were tracked in git - Add root node_modules/ to .gitignore - Add SECURITY.md with vulnerability reporting policy node_modules was bloating clone size and is a red flag for experienced OSS reviewers.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Pre-launch cleanup
Critical: node_modules tracked in git
186 packages (23MB, 4800+ files) were committed to the repo. This:
Removed and added
node_modules/to.gitignore.Added: SECURITY.md
Security-focused project needs a vulnerability reporting policy. Added standard SECURITY.md with:
Note: Vercel OIDC tokens in git history
The
.env.localfiles removed in PR #17 contained Vercel OIDC JWTs. These expired Jan 1, 2026 — not exploitable. But they do leak:team_ep8LEiBkDAKDemVrjAxBdQRMprj_71ZThcMGhIjThGdG69e15QTDNTlfNot urgent but worth noting. A future
git filter-repocould clean history.