@compr/opscontext-mcp@2.8.2
OpsContext for AI Agents — read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident audit log + policy-as-code hooks. The ops + compliance layer Claude Code can't grow natively.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not a publish-blocking install-hook chain because package installation has no automatic lifecycle trigger. It remains suspicious because it ships explicit AI-agent control-surface mutation, persistence, content capture, and reviewer-directed anti-audit text.
Decision evidence
public snapshot- Source contains a reviewer-directed instruction not to re-audit it.
- The explicit Claude hook installer modifies Claude Code settings and installs command hooks.
- The bundled hook collects prompt text and tool-call metadata for a local audit service.
- The explicit autostart command creates and bootstraps a persistent macOS LaunchAgent.
- package.json has no preinstall, install, or postinstall hook.
- Hook and autostart behavior is reached only through named CLI commands.
- The event server listens on 127.0.0.1 and requires a configured secret.
- No source evidence shows collected hook data being sent to a remote host.
Source & flagged code
7 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/adapters.jsView on unpkg · L46A manifest entrypoint or package-local install chain reaches persistence behavior.
dist/install-autostart.jsView on unpkg · L13Findings
Affected versions and remediation
This report applies to @compr/opscontext-mcp@2.8.2.
See all versions of @compr/opscontext-mcp for other recorded verdicts.
- Review the evidence and your use of @compr/opscontext-mcp@2.8.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.