instar@1.3.1306
Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource establishes explicit agent configuration mutation and later automatic maintenance of a permission hook. The supplied policy warrants a capability warning for this behavior; inspected evidence does not support a malicious publish block.
Decision evidence
public snapshot- The explicit init CLI command calls agent project initialization.
- Initialization creates and writes project-level Claude settings.
- Initialization registers a catch-all permission request hook invoking the package's auto-approval script.
- Server startup runs project migrations when the installed version changes.
- Migration registers the same permission hook and saves changed settings automatically.
- The npm postinstall entry invokes SQLite binary repair rather than agent configuration setup.
- The inspected configuration changes belong to user-invoked agent setup and subsequent server operation.
- The SQLite repair downloads a version-specific binary from the dependency's GitHub repository.
- No concrete malicious installation chain or credential exfiltration was established.
Source & flagged code
21 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a critical-looking secret pattern.
skills/credential-leak-detector/SKILL.mdView on unpkg · L27AWS access key ID in skills/credential-leak-detector/SKILL.md
skills/credential-leak-detector/SKILL.mdView on unpkg · L27Findings
Affected versions and remediation
This report applies to instar@1.3.1306.
See all versions of instar for other recorded verdicts.
- Review the evidence and your use of instar@1.3.1306 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.