instar@1.3.1409
⚠ Under reviewCoherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected source does not substantiate the scanner’s most serious claims: the GitSync excerpt manages public Git signing keys, and Telegram credentials are sent to Telegram’s API. The package’s large runtime surface could not be resolved within the required citation coverage, so a full clean determination is not supported.
Decision evidence
public snapshot- The manifest’s install hooks run a better-sqlite3 repair script and Husky setup; prepublishOnly runs build and release checks.
- GitSync writes active machine public signing keys to an allowed-signers file for Git verification.
- Telegram setup sends the supplied bot token to Telegram’s getChat endpoint, and the adapter constructs API requests for api.telegram.org.
- The inspected excerpts do not establish the flagged credential redirect or a remote access backdoor.
- Static hints identify additional large runtime files and review targets whose behavior was not resolved in this inspection.
- The inspected source excerpts do not establish the behavior of the package’s full runtime surface.
Source & flagged code
17 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
dist/threadline/PipeSessionSpawner.jsView on unpkg · L15Package source references shell execution.
Findings
Affected versions and remediation
This report applies to instar@1.3.1409.
See all versions of instar for other recorded verdicts.
- Review the evidence and your use of instar@1.3.1409 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.