registry / @cotal-ai/cli / 0.135.14
@cotal-ai/cli@0.135.14
Cotal mesh CLI: up, join, watch, console, spawn, mint, channels, history, ext.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest declares no install lifecycle hook, and the reviewed runtime actions are tied to explicit commands or to adding the package's own staged connectors. Skill writes are limited to Cotal-authored files under ~/.agents/skills and are triggered by cotal setup.
Static reason
One or more suspicious static signals were detected.
Trigger
Feedback and joining require their respective user commands; skill installation runs through cotal setup, optionally with --skills.
Impact
The inspected behavior does not show unsolicited credential collection, unrelated data transmission, or unauthorized account actions.
Mechanism
Feedback submits user-provided content to the Cotal intake. Setup reconciles Cotal-authored skill files with bounded file-level writes. Connector seeding invokes the CLI to add its staged package.
AI rationale
The manifest declares no install lifecycle hook, and the reviewed runtime actions are tied to explicit commands or to adding the package's own staged connectors. Skill writes are limited to Cotal-authored files under ~/.agents/skills and are triggered by cotal setup.
Evidence
~/.agents/skills/<name>/SKILL.md~/.agents/skills/<name>/SKILL.md.bak
Network endpoints2
broker.cotal.ai/v1/feedbackcotal.ai/v1/feedback
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package has no install or postinstall lifecycle hook; its main entry is dist/index.js.
- Agent skills are written only when the user runs cotal setup, and the skills-only path is explicitly selected with --skills.
- Skill reconciliation manages Cotal-authored SKILL.md files under ~/.agents/skills, preserving backups and limiting changes to those files.
- Feedback is sent by an explicit command using the supplied summary and details; a configured feedback key is sent to the Cotal feedback intake.
- Join channel selection occurs inside the explicit cotal join command.
Evidence against
- The package has runtime process execution and network access, but inspected uses support connector seeding, user-selected setup, feedback submission, and joining.
- The setup command may install skills into an AI-agent skill directory, but that behavior is triggered by the user's setup command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystem
Source & flagged code
6 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
5 High4 Medium4 Low
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.14.
See all versions of @cotal-ai/cli for other recorded verdicts.
- Review the evidence and your use of @cotal-ai/cli@0.135.14 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.