@compr/opscontext-mcp@2.8.3
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 explicit Claude hook setup is a concrete agent configuration capability, so this warrants a warning. The package has no npm install lifecycle trigger for that setup, and the inspected sources do not establish a publish-blocking attack.
Decision evidence
public snapshot- The manifest defines only a prepublishOnly lifecycle script; the flagged setup is not wired to npm install.
- The CLI exposes Claude hook installation as an explicit command.
- That command copies a hook script into the user's Claude hooks directory and updates settings.json.
- The installer adds hooks for prompt submission, tool use, and session start.
- The activation source contains a comment instructing reviewers not to re-audit it, which is reviewer-directed manipulation.
- The hook setup runs through an explicit CLI command rather than an npm install hook.
- The installer backs up settings.json and deduplicates existing hook registrations.
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.3.
See all versions of @compr/opscontext-mcp for other recorded verdicts.
- Review the evidence and your use of @compr/opscontext-mcp@2.8.3 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.