@su-record/vibe
Your personal FDE in Claude and Codex. Understand the work, use the right tools, deliver and retain useful context. One entry: vibe.
This report shows the evidence for @su-record/vibe@4.2.1. 56 of 83 known versions are blocked or flagged. The newest version, 4.2.23, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has a concrete automatic postinstall chain that modifies multiple AI-agent homes and installs hooks, rather than requiring an explicit setup command. This meets the install-control-surface blocking policy even though this inspection found no secret exfiltration or self-dependency chain.
Decision evidence
public snapshot- The package declares an automatic postinstall lifecycle script.
- On global installation, postinstall calls setupGlobal without an interactive consent step.
- setupGlobal installs cards, skills, and command hooks into detected Claude, Codex, and Hermes user homes.
- The installed hook configuration runs the package's notify script for PreToolUse, Stop, and SessionStart.
- The package also writes a local plugin entry into the shared agent marketplace.
- No runtime dependency on @su-record/vibe itself is declared.
- The reviewed notification hook contains no network request or credential-exfiltration code.
- The GitHub client uses the GitHub API only when its corresponding runtime feature is invoked.
Source & flagged code
18 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
mcpb/server/index.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @su-record/vibe@4.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @su-record/vibe@4.2.1. 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.