@rigxyz/cli@0.14.2
Portable, runnable agent workspaces
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected hook installs a first-party package-owned agent extension automatically, which the supplied policy classifies as warning-only lifecycle risk. Its scoped destination, collision guard, and opt-out do not establish malicious intent or justify blocking.
Decision evidence
public snapshot- package.json automatically runs bin/postinstall.mjs after installation.
- The hook writes a Rig-owned SKILL.md under agent skill directories, defaulting to the user's home directory.
- Installation targets .claude and .agents without a consent prompt; RIG_SKIP_SKILL_INSTALL disables it.
- Existing skills without the package ownership marker are preserved.
- A matching skill version skips rewriting; subsequent installations can update the managed skill.
- The explicit workspace installation command also writes project agent guidance and merges manifest permissions while preserving denies.
- The automatic extension is confined to the package-owned rig skill rather than broad agent settings.
- No concrete malicious payload execution, credential theft, or destructive install behavior was established.
Source & flagged code
12 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 unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/collab.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @rigxyz/cli@0.14.2.
See all versions of @rigxyz/cli for other recorded verdicts.
- Review the evidence and your use of @rigxyz/cli@0.14.2 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.