@cotal-ai/connector-jcode@0.140.1
Cotal connector for Jcode: a host-mode mesh peer driven through Jcode's Harness API bridge.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe connector's purpose explains launching Jcode, but its host automatically mirrors recognized third-party credential stores and the SDK inherits logins by default. Since the inspected source does not establish where those credentials go, this is a warning-level credential-forwarding risk rather than a confirmed exfiltration attack.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall script; it exports the connector entry point.
- The host requires a Cotal managed-session control endpoint before it starts.
- At host startup, the connector calls `mirrorJcodeCredentials(home)` without a visible opt-in check.
- The SDK recognizes credential files from Claude, Codex, Gemini, Cursor, and other agent tools.
- The SDK inherits logins by default and launches Jcode's API bridge with the process environment.
- The package describes itself as a Cotal connector for Jcode, so starting Jcode and making its configured logins available are consistent with its purpose.
- The inspected source does not establish a foreign network destination receiving those credentials.
Source & flagged code
11 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/host.jsView on unpkg · L111Findings
Affected versions and remediation
This report applies to @cotal-ai/connector-jcode@0.140.1.
See all versions of @cotal-ai/connector-jcode for other recorded verdicts.
- Review the evidence and your use of @cotal-ai/connector-jcode@0.140.1 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.