@cotal-ai/connector-jcode@0.141.0
Cotal connector for Jcode: a host-mode mesh peer driven through Jcode's Harness API bridge.
AI Security Review
scanned 19h ago · by lpm-firewall-aiThe flagged credential access is part of preparing a private Jcode seat, and the inspected flow starts a local Jcode API bridge without evidence of sending those credentials to an unrelated host. The package has no install hook, and its Cotal network paths serve feedback and documentation features.
Decision evidence
public snapshot- The package entry is dist/index.js; package.json defines build, bundle, typecheck, and test scripts, with no install lifecycle hook.
- Import registers a connector; its buildLaunch function returns a separate host process to run when the connector launches.
- The host mirrors recognized credential files into the seat’s private Jcode home, then starts Jcode’s local API bridge with login inheritance disabled. No unrelated credential transmission was identified.
- Feedback uses Cotal’s feedback endpoints and requires an email for keyless submissions; remote documentation is fetched from docs.cotal.ai.
- The host automatically reads and copies recognized local provider credential stores when it starts; this is sensitive behavior, but the inspected flow places them in the local Jcode seat home and shows no unrelated collector.
- The package includes a compressed documentation bundle that was not needed to assess the executable credential flow.
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.0.
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.0 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.