registry / @cotal-ai/cli / 0.135.2
@cotal-ai/cli@0.135.2
Cotal mesh CLI: up, join, watch, console, spawn, mint, channels, history, ext.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process execution and configuration writes occur through explicit CLI operations. The reviewed credential flows use user-provided inputs for the relevant service features, with no evidence of unrelated exfiltration or hidden account actions.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Extension installation, setup reconciliation, feedback submission, and joining are invoked through their respective CLI commands.
Impact
No malicious impact identified.
Mechanism
The inspected operations are user-triggered and align with the CLI’s stated purpose; the skills reconcile is limited to its managed skill files.
AI rationale
The manifest has no install lifecycle hook, and the flagged process execution and configuration writes occur through explicit CLI operations. The reviewed credential flows use user-provided inputs for the relevant service features, with no evidence of unrelated exfiltration or hidden account actions.
Evidence
~/.agents/skills/<name>/SKILL.md
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no preinstall, install, or postinstall lifecycle hook; its scripts are development commands.
- Extension installation runs through the explicit `ext add` command; the internal replay path checks that its parent owns the update pass.
- The shared Agent Skills reconcile is exposed as `setup --skills` and writes Cotal-authored `SKILL.md` files under `~/.agents/skills`, with safeguards for symlinks and divergent user files.
- Feedback sends a credential only through the explicitly invoked feedback command to its selected intake URL.
- The join command uses credentials and space details supplied through its flags, link, or credentials file.
Evidence against
- The scanner’s shell and child-process findings correspond to CLI extension/setup operations, not install-time execution.
- The Agent Skills write is a disclosed setup feature scoped to the package’s own skill files.
- No credential theft, unrelated collector, hidden account action, or automatic destructive behavior was identified.
Behavioral surface
ChildProcess
Source & flagged code
7 flaggeddist/seed/reconcile.jsView file
1import { existsSync, renameSync } from "node:fs";
L2: import { spawnSync } from "node:child_process";
L3: import { randomBytes } from "node:crypto";
High
Child Process
Package source references child process execution.
dist/seed/reconcile.jsView on unpkg · L1dist/lib/persona-files.jsView file
274process.on(signal, pass);
L275: const child = program ? spawn(program, [draft], { stdio: "inherit" }) : spawn(`${editor} ${quoted}`, { shell: true, stdio: "inherit" });
L276: return new Promise(resolve => {
High
dist/lib/nats-bin.jsView file
Findings
1 Critical5 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/ext.js
HighChild Processdist/seed/reconcile.js
HighShelldist/lib/persona-files.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/lib/agent-skills.js
HighRuntime Package Installdist/commands/setup.js
HighSemantic Analysis Limiteddist/commands/ext.js
MediumDynamic Requiredist/lib/nats-bin.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @cotal-ai/cli@0.135.2.
See all versions of @cotal-ai/cli for other recorded verdicts.
- Review the evidence and your use of @cotal-ai/cli@0.135.2 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.