@agent-link/agent@0.1.339
AgentLink local agent CLI
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection found a narrowly gated runtime migration in the global postinstall path and product-aligned runtime behavior. The flagged agent paths resolve to project/session data, while persistent service setup is presented as an explicit CLI action.
Decision evidence
public snapshot- The manifest’s postinstall invokes the bridge, while the hook runs it only for global npm installs.
- The bridge skips unless an existing version store is adopted and complete and the installed version is newer; it prepares a runtime migration for that store.
- The indicated Claude and Codex locations resolve to project history, project memory, and session directories, not global agent settings or plugin locations.
- The inspected runtime hints cover executable path lookup, work-directory file upload, Git status parsing, and local backend text or attachment handling.
- The service code selects user-level service artifact locations, and the CLI presents service installation as an explicit command.
- The configured relay defaults to the product service, and the connection sends a configured password as relay authentication.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references weak cryptographic algorithms.
dist/emergency-upgrade.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @agent-link/agent@0.1.339.
See all versions of @agent-link/agent for other recorded verdicts.
- Review the evidence and your use of @agent-link/agent@0.1.339 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.