superclawd@0.1.86
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 2mo ago · by lpm-firewall-aiThere is no automatic npm lifecycle trigger or self-dependent release chain, so blocking is not supported. However, the explicit CLI command creates persistent project hooks and transmits prompt- and repository-derived information to a remote service, which warrants a warning.
Decision evidence
public snapshot- The normal CLI path installs a Git post-commit hook in the current project.
- That hook reads the committed Git patch and reports derived results to the vendor API.
- Session hooks send up to 500 characters of user prompts to the vendor memory-search endpoint.
- The CLI creates a Claude Code plugin that loads remote directives and registers hooks.
- package.json has no preinstall, install, or postinstall hook.
- The behavior is reached when the user runs the superclawd CLI, not when npm installs it.
- The source uses named SuperClawd API hosts and authenticated service requests rather than an opaque payload host.
- No runtime dependency on superclawd itself is declared.
Source & flagged code
7 flaggedPackage source references a known benign dynamic code generation pattern.
dist/mcp-server.mjsView on unpkg · L5Findings
Affected versions and remediation
This report applies to superclawd@0.1.86.
See all versions of superclawd for other recorded verdicts.
- Review the evidence and your use of superclawd@0.1.86 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.