@agent-link/agent@0.1.338
AgentLink local agent CLI
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe global install hook can stage and activate a newer runtime when prior adoption is complete, so the guarded lifecycle capability warrants a warning. The flagged agent integration locations inspected access session and project-memory paths and did not establish broader agent configuration mutation.
Decision evidence
public snapshot- The npm postinstall runs an installer bridge; that hook runs its migration only for global installs.
- The bridge skips unless version-store adoption is complete and the package version is newer, then stages a runtime and updates its version pointer.
- A manifest URL override must be loopback, and the manifest validates supported package, platform, architecture, and bundle fields.
- The Codex and Claude integration locations inspected resolve session and project-memory paths; they do not show config mutation.
- Service persistence is exposed through an explicit CLI service install command.
- A global npm postinstall can fetch and stage a package runtime and modify the active version pointer when migration conditions are met.
Source & flagged code
5 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.338.
See all versions of @agent-link/agent for other recorded verdicts.
- Review the evidence and your use of @agent-link/agent@0.1.338 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.