@compr/opscontext-mcp@2.13.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 source shows explicit user-command setup that can persist behavior in Claude configuration and the user's login session, so a capability warning is appropriate. No unconsented install-time mutation or other concrete attack behavior was established.
Decision evidence
public snapshot- The manifest defines no preinstall, install, or postinstall hook; its prepublishOnly script runs during publishing.
- Explicit CLI commands invoke the Claude hook installer and autostart installer.
- The Claude hook installer can write hook configuration to the user's ~/.claude/settings.json.
- The autostart installer writes a LaunchAgent plist and bootstraps it for the user's login session.
- The bundled skill installer writes a package-owned skill file into a selected Claude skill directory.
- The inspected agent configuration changes are reached through explicit CLI commands, not an npm install lifecycle hook.
- The hook installer avoids writing settings when unchanged, and the skill installer protects an existing skill unless --force is supplied.
Source & flagged code
7 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.13.0.
See all versions of @compr/opscontext-mcp for other recorded verdicts.
- Review the evidence and your use of @compr/opscontext-mcp@2.13.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.