@compr/opscontext-mcp@2.16.0
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 12d ago · by lpm-firewall-aiThe reviewer-directed instruction is evidence of malicious intent under the review policy, so the package is suspicious. Its manifest and CLI structure do not establish a publish-blocking install-time attack.
Decision evidence
public snapshot- dist/activation.js contains a direct instruction telling reviewers not to re-audit the activation code; this is reviewer manipulation.
- package.json has no preinstall, install, or postinstall script; its prepublishOnly script is not an install trigger.
- The autostart and Claude hook setup are exposed as explicit CLI commands.
- The Claude hook installer writes OpsContext hook entries under the user's Claude settings; no automatic npm-triggered write was identified.
- The agent, Claude integration, CLI, secrets-lock, shared-index, autostart, and activation target locations were inspected; their cited excerpts show agent discovery, package-owned skill paths, settings reads, shared-index behavior, CLI setup, and activation comments.
- No concrete credential theft, exfiltration, destructive behavior, or unconsented install-time control-surface mutation was established.
Source & flagged code
6 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/adapters.jsView on unpkg · L47A 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.16.0.
See all versions of @compr/opscontext-mcp for other recorded verdicts.
- Review the evidence and your use of @compr/opscontext-mcp@2.16.0 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.