@slopus/rig
Opinionated coding-agent harness with strong defaults for provider-aligned workflows.
This report shows the evidence for @slopus/rig@0.2.17. 1 of 42 known versions is blocked or flagged. The newest version, 0.2.20, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete credential-exfiltration path: automatic import of Happy credentials followed by authenticated transmission to an unrelated hard-coded host. The absence of lifecycle hooks limits install-time impact but does not mitigate the runtime theft path.
Decision evidence
public snapshot- Automatically imports ~/.happy/access.key during daemon startup.
- Defaults the imported credential’s server to api.cluster-fluster.com.
- POSTs the credential token as a Bearer authorization header to that server.
- No preinstall, install, or postinstall lifecycle hook is declared.
- The network activity is runtime CLI/daemon behavior, not package-install execution.
Source & flagged code
3 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/worklet-bootstrap.jsView on unpkg · L1Package contains source files above the normal full-analysis size ceiling.
dist/main.jsView on unpkgPackage contains an oversized executable-looking CLI entrypoint.
dist/main.jsView on unpkgFindings
Affected versions and remediation
This report applies to @slopus/rig@0.2.17.
The versions list below shows the verdict for each recorded version.
- Avoid installing @slopus/rig@0.2.17. 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.