instar@1.3.1332
Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe source supports a warning for package-owned agent configuration that changes Claude project memory locations. The manifest’s postinstall hook is a separate native dependency repair script, and the inspected migration is scoped to the Instar project.
Decision evidence
public snapshot- The postinstall hook runs a native dependency repair script; it does not invoke the agent-memory migration.
- The post-update migrator links memory for the Instar project into every discovered Claude config home.
- The memory helper only acts for an Instar agent home and its own project, and skips memory links outside that agent’s home.
- The package also contains Claude-specific setup, migration, and session-related code at the inspected integration locations.
- The memory migration can move an existing project memory directory aside after merging it, then replace it with a symlink.
- The inspected migration is package-owned runtime agent configuration behavior; no install-time trigger or credential transfer was established.
Source & flagged code
18 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.1332.
See all versions of instar for other recorded verdicts.
- Review the evidence and your use of instar@1.3.1332 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.