bumper-guard
A plain-language safety net for vibe coders. Pauses risky things your AI assistant (Claude Code, Cursor, Copilot CLI) is about to do, explains them in plain English, and lets you decide.
This report shows the evidence for bumper-guard@0.2.13. 12 of 12 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic lifecycle chain modifies foreign global AI-agent configurations and establishes persistent background execution. This meets the install-hook abuse blocking policy even though direct external exfiltration of hook data was not found.
Decision evidence
public snapshot- The postinstall hook automatically detects installed AI tools, globally wires their hook configurations, starts a detached daemon, and enables login persistence.
- Global Claude Code integration appends a command hook for every pre-tool action to the user's settings file.
- Global Cursor integration adds shell and MCP hooks to the user's Cursor configuration.
- The install path creates operating-system login persistence through launchd, systemd, or the Windows Startup folder.
- The daemon records complete hook requests, including commands, file paths, and content, in a user-home audit log.
- No runtime dependency on another release of this package was found.
- The only external service code inspected is account and quota traffic; no direct remote upload of captured hook requests was found.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to bumper-guard@0.2.13.
The versions list below shows the verdict for each recorded version.
- Avoid installing bumper-guard@0.2.13. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.