registry / @theronap/agnoclast-mcp / 0.9.230
@theronap/agnoclast-mcp@0.9.230
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-aiSource inspection found no npm install hook or concrete attack behavior. The flagged configuration and watcher changes are part of explicit setup or cleanup commands, so the package is clean.
Static reason
No blocking static signals were detected.
Trigger
A user explicitly invokes setup, install, or uninstall; the manifest declares no npm lifecycle hook.
Impact
The inspected behavior supports the package’s assistant integration and cleanup functions; no concrete attack effect was established.
Mechanism
The commands wire or remove Agnoclast-owned assistant configuration and skills. Antigravity setup writes watcher artifacts and reports that activation requires a separate step.
AI rationale
Source inspection found no npm install hook or concrete attack behavior. The flagged configuration and watcher changes are part of explicit setup or cleanup commands, so the package is clean.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and lists only release, promote, and rollback scripts; no npm lifecycle hook is declared.
- The CLI dispatches setup, install, and uninstall when those commands are invoked.
- Setup and editor adapters write Agnoclast configuration to assistant-specific locations; the Codex adapter skips wiring without a token.
- Skills are installed into Claude and Codex skill directories, uninstall removes managed entries, and transcript lookup uses a session ID under Claude project folders.
- Antigravity setup writes a watcher script and plist but does not load the watcher; it warns that the script depends on a local development checkout.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedlib/capture.mjsView file
1import { readFileSync, accessSync, constants, openSync, mkdirSync } from 'fs'
L2: import { spawn, execFileSync } from 'child_process'
L3: import { homedir } from 'os'
...
L21: if (!res.ok) return null
L22: const j = await res.json().catch(() => ({}))
L23: return Array.isArray(j.types) ? j.types : null
...
L35: try {
L36: if (resolve(String(cwd)) === homedir()) return 'general'
L37: } catch { /* unresolvable path — fall through to basename */ }
...
L45: //
L46: // Handles the four remote forms git emits: scp-like ssh (git@github.com:o/n.git), ssh://, https://,
L47: // git://. The HOST CHECK IS LOAD-BEARING, not cosmetic: this string becomes a clearance key, and
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/capture.mjsView on unpkg · L1lib/editors/antigravity.mjsView file
4Trigger-reachable persistence chain: manifest.bin -> bin/cortex-mcp.mjs -> lib/install.mjs -> lib/editors/index.mjs -> lib/editors/antigravity.mjs
L4: // WatchPaths the trajectory store and runs a one-shot sync. wire() generates the two artifacts
L5: // (the sync.sh + the launchd plist) deterministically. It does NOT run `launchctl load` here
L6: // (an unverifiable system mutation) and it flags the PORTABILITY BLOCKER below.
...
L21: /** The launchd plist, home-substituted. Deterministic — golden-testable byte-for-byte. */
L22: export function renderAntigravityPlist({ home = homedir() } = {}) {
L23: const sh = join(home, '.cortex', 'antigravity-sync.sh')
...
L33: <array>
L34: <string>/bin/bash</string>
L35: <string>${sh}</string>
Findings
3 High3 Medium6 Low
HighTrigger Reachable External Ai Agent Control Surface Mutationlib/uninstall.mjs
HighTrigger Reachable Persistencelib/editors/antigravity.mjs
HighSemantic Analysis Limitedbin/cortex-mcp.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencelib/editors/antigravity.mjs
LowScripts Present
LowWeak Cryptolib/capture.mjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @theronap/agnoclast-mcp@0.9.230.
See all versions of @theronap/agnoclast-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/agnoclast-mcp@0.9.230 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.