@cotal-ai/connector-jcode@0.132.6
Cotal connector for Jcode: a host-mode mesh peer driven through Jcode's Harness API bridge.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged execution and credential access are part of the package’s stated Jcode connector behavior: the host prepares a private Jcode home and launches a local bridge. No install hook or source evidence of credential exfiltration or other attack behavior was found.
Decision evidence
public snapshot- The manifest describes this as a Cotal connector driven through Jcode’s Harness API and declares no install lifecycle hook.
- When the connector host starts, it mirrors recognized Jcode and provider credential files into a private Jcode home, then launches the local Jcode API bridge.
- The bridge launch disables the SDK’s separate login inheritance; I found no source path that sends the mirrored credentials to Cotal.
- Host startup automatically copies recognized credentials from Jcode, provider config, and other agent login stores into the connector’s private Jcode home.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/host.jsView on unpkg · L49Findings
Affected versions and remediation
This report applies to @cotal-ai/connector-jcode@0.132.6.
See all versions of @cotal-ai/connector-jcode for other recorded verdicts.
- Review the evidence and your use of @cotal-ai/connector-jcode@0.132.6 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.