Skip to content

chore: update package.json for canary test#18

Open
pullfrog[bot] wants to merge 25 commits intomainfrom
pullfrog/update-package-json
Open

chore: update package.json for canary test#18
pullfrog[bot] wants to merge 25 commits intomainfrom
pullfrog/update-package-json

Conversation

@pullfrog
Copy link
Copy Markdown

@pullfrog pullfrog Bot commented Apr 19, 2026

Updates package.json as part of the dependency installation canary test — replaces the original repo metadata with the test fixture used to probe postinstall script execution behavior.

Pullfrog  | via Pullfrog | Using Claude Opus𝕏


Note

Medium Risk
Adds a postinstall script that writes to /tmp, which will execute during dependency installation and could affect CI/build environments. Scope is limited to package.json but changes install-time behavior.

Overview
Switches package.json from a minimal private test project to a published-style package (name/version) and removes the vitest test script.

Adds a postinstall hook that writes CANARY_MARKER to /tmp/postinstall-canary.txt to probe install-time script execution, and sets an explicit empty dependencies object.

Reviewed by Cursor Bugbot for commit bd93265. Bugbot is set up for automated code reviews on this repo. Configure here.

Comment thread package.json
}
"postinstall": "echo CANARY_MARKER > /tmp/postinstall-canary.txt"
},
"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 flag risks accidental npm publish

Medium Severity

The original package.json had "private": true which prevents accidental publishing to npm. The replacement drops this field entirely while also giving the package a publishable name (test-pkg) and version (1.0.0). Running npm publish — even accidentally — would now succeed rather than being blocked.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a71fb22. Configure here.

Comment thread package.json
"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, breaking existing test execution

Medium Severity

The "test": "vitest run" script was replaced entirely by the postinstall script. The repo still contains test/math.test.ts which imports from vitest, so npm test will now fail with a missing script error. The canary postinstall entry could coexist alongside the original test script instead of replacing it.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a71fb22. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit e22785c. Configure here.

Comment thread package.json
}
"postinstall": "echo CANARY_MARKER > /tmp/postinstall-canary.txt"
},
"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.

Test fixture overwrites project config, breaking existing tests

Medium Severity

The "test": "vitest run" script and "type": "module" declaration were removed and replaced with only a postinstall canary script. The repo still contains vitest tests (test/math.test.ts) and ESM source files (src/*.ts using export), so npm test is now broken and module resolution for the existing code may fail. This looks like a test fixture that's replacing the real project configuration.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e22785c. Configure here.

pullfrog Bot added 18 commits May 5, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants