@kryptosai/mcp-observatory@1.44.0
MCP security scanner and CI gate. Test, secure, and monitor MCP servers with attack simulation, schema drift detection, health scoring, and SARIF before agents depend on them.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source confirms a postinstall hook, but its project checks and explicit auto-setup gate constrain its workflow write. The flagged files inspected show package-aligned scanner and reporting behavior, with no concrete attack behavior found.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs scripts/postinstall.mjs.
- The postinstall exits for self-installs and CI, and only proceeds for a recognized MCP project.
- Automatic CI workflow creation requires an explicit environment or package configuration opt-in.
- The handshake helper discovers MCP configuration paths; discovery alone does not write them.
- The flagged source files contain scanner, reporting, hashing, and diagnostic logic consistent with package functionality.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/src/ci-issue.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @kryptosai/mcp-observatory@1.44.0.
See all versions of @kryptosai/mcp-observatory for other recorded verdicts.
- Review the evidence and your use of @kryptosai/mcp-observatory@1.44.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.