@cotal-ai/connector-jcode@0.141.10
Cotal connector for Jcode: a host-mode mesh peer driven through Jcode's Harness API bridge.
AI Security Review
scanned 5h ago · by lpm-firewall-aiAutomatic staging of credentials from multiple unrelated tools creates a real exposure risk, and the source does not show a consent control for that transfer. I found no evidence that the copied credentials leave the local Jcode process, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The host bundles credential paths for Claude, Codex, Gemini and Cursor, including Cursor state databases.
- When the host prepares a Jcode seat, it calls mirrorJcodeCredentials before starting the Jcode instance.
- The package describes itself as a Jcode Harness API connector.
- The credential mirror implementation inventories credentials from the user's Jcode home, app config and external home.
- The manifest has no install, preinstall or postinstall lifecycle script.
- The inspected code shows credentials being staged for a local Jcode instance, but does not establish that the copied credentials are transmitted to an unrelated host.
- The connector's stated purpose involves launching Jcode through its Harness API bridge.
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.141.10.
See all versions of @cotal-ai/connector-jcode for other recorded verdicts.
- Review the evidence and your use of @cotal-ai/connector-jcode@0.141.10 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.