Skip to content
Open
Changes from 13 commits
Commits
Show all changes
15 commits
Select commit Hold shift + click to select a range
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
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"
},
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Test script removed while test files still exist

Low Severity

The "test": "vitest run" script was deleted and replaced solely with a postinstall script. The test file test/math.test.ts still imports from vitest and expects to be runnable, so npm test now produces an error instead of running the existing test suite. The postinstall canary could have been added alongside the existing test script rather than replacing it.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 0f8cb09. Configure here.

"dependencies": {}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Removal of private field risks accidental npm publish

Medium Severity

The "private": true field was removed from package.json. This safety guard prevents accidental publication to the npm registry. Without it, an npm publish (manual or via CI misconfiguration) would push this test package publicly, which could also enable a dependency-confusion vector since the name test-pkg is generic.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 0f8cb09. Configure here.

}