@su-record/vibe@4.2.13
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 6d ago · by lpm-firewall-aiThe package automatically installs its own AI client integrations after global npm installation, so a residual agent extension lifecycle risk remains. The inspected behavior does not establish a publish-blocking attack.
Decision evidence
public snapshot- package.json runs scripts/postinstall.js during installation.
- The postinstall exits unless npm reports a global install and VIBE_SKIP_SETUP is unset, then calls setupGlobal.
- setupGlobal installs surfaces for detected client homes; fallback surfaces add a card, skill, and hook.
- For Claude with its CLI available, setup registers the package as a plugin; the cited plugin installer assembles its local tree.
- The cited register.js location reads Claude's installed plugin state.
- The reviewed hook is limited to global npm installs and can be skipped with VIBE_SKIP_SETUP.
- The reviewed setup uses package-owned client integrations; these excerpts do not establish credential transfer or an unrelated recipient.
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.13.
See all versions of @su-record/vibe for other recorded verdicts.
- Review the evidence and your use of @su-record/vibe@4.2.13 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.