@su-record/vibe@4.2.12
Your personal FDE in Claude and Codex. Understand the work, use the right tools, deliver and retain useful context. One entry: vibe.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found a postinstall-triggered global integration setup that writes first-party AI client surfaces, a guarded lifecycle capability that warrants a warning. The scanner’s similarity labels alone do not prove maliciousness, and inspected runtime code showed no separate concrete attack behavior.
Decision evidence
public snapshot- The manifest runs scripts/postinstall.js after installation.
- The postinstall script only proceeds for global npm installs and can be disabled with VIBE_SKIP_SETUP.
- Global setup installs integration surfaces for detected clients in the user home.
- The Codex plugin writes a local plugin tree and adds or updates its entry in the personal marketplace while preserving other plugins.
- The MCP server forwards selected CLI commands in the chosen project directory; inspected source showed no independent payload or credential exfiltration behavior.
- Scanner source similarity labels do not establish malicious behavior; the inspected flagged code showed package integration and ordinary CLI functionality.
- A global npm install automatically triggers setup that writes integrations into detected AI client homes; no separate setup confirmation appears in the postinstall path. This is a guarded first-party agent integration lifecycle risk.
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.12.
See all versions of @su-record/vibe for other recorded verdicts.
- Review the evidence and your use of @su-record/vibe@4.2.12 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.