Skip to content

chore: update package.json for postinstall canary test #35

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.

Sign up for GitHub

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

Open
pullfrog wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: update package.json for postinstall canary test #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"name": "test-repo",
"private": true,
"type": "module",
"name": "test-pkg",
"version": "1.0.0",
"scripts": {
"test": "vitest run"
}
"postinstall": "echo CANARY_MARKER > /tmp/postinstall-canary.txt"
},
"dependencies": {}

@cursor cursor Bot May 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing private: true risks accidental npm publish

Medium Severity

The "private": true field was removed from package.json without being mentioned in the PR description. This safety guard prevents accidental publication to the npm registry. Without it, running npm publish (even accidentally) could push test-pkg@1.0.0 to the public npm registry — potentially causing a supply-chain concern or namespace squatting. Since the package is a test fixture and not meant to be published, "private": true is worth keeping.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit b941043. Configure here.

}