@theronap/cortex-mcp@0.9.233
Renamed to @theronap/agnoclast-mcp — use that. Existing installs switch themselves to the new name on next start.
Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no npm lifecycle hook, and the persistence finding is an explicit setup artifact that is not activated automatically. However, setup enables later automatic installation of organization-published agent instructions without per-skill approval, leaving a bounded agent-extension lifecycle risk.
Decision evidence
public snapshot- package.json declares no install lifecycle hook; the CLI dispatches setup, install, and uninstall as explicit commands.
- Antigravity wiring runs only through the install command; it writes a launch agent with RunAtLoad disabled and does not activate it.
- The reviewed editor adapters and helpers target their named editor configuration, managed skills, or transcript files.
- Setup and session repair fetch authenticated org-published skills from the package’s service and install them into detected Claude and Codex skill directories.
- Claude setup adds a SessionStart skills-repair command, which can refresh org-published skills in later sessions without a per-skill approval step.
- The Antigravity artifact is inert until the user manually loads it, and its generated sync script depends on a local development checkout.
Source & flagged code
6 flaggedPackage source references weak cryptographic algorithms.
lib/capture.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @theronap/cortex-mcp@0.9.233.
See all versions of @theronap/cortex-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/cortex-mcp@0.9.233 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.