superclawd@0.1.35
Claude Code, supercharged — your team's standards, every session. The superclawd CLI loads your workspace's skills, agents, commands, workflows, and live directives into Claude Code as a plugin.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not concrete malicious npm-install behavior, but its explicit CLI path installs persistent Git/Claude lifecycle hooks and transmits captured workspace-memory content. Warn so users can assess the continuing agent and repository control surface.
Decision evidence
public snapshot- On explicit CLI use in a Git repo, writes an executable post-commit hook that runs in the background.
- Claude session hooks capture condensed user, assistant, tool-input, and tool-result transcript content.
- Captured memory operations are sent to the package’s authenticated MCP API.
- No npm preinstall/install/postinstall hook; the sole lifecycle hook is prepublishOnly.
- The control-surface changes occur only after the user runs the CLI, and an existing non-SuperClawd post-commit hook is preserved.
- Endpoints and behavior align with the documented workspace-memory and Claude-plugin product.
Source & flagged code
7 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/index.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to superclawd@0.1.35.
See all versions of superclawd for other recorded verdicts.
- Review the evidence and your use of superclawd@0.1.35 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.