@proagentstore/cli@0.4.96
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected network and subprocess operations are tied to the CLI's own authentication, update, and runner functionality. Scanner flags alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json declares build, development, and typecheck scripts; no install lifecycle hook is present.
- The flagged source checks a requested `up` command before fetching and loading an updated CLI payload.
- The update helper queries and installs a release of this same CLI package into a separate prefix.
- The login command sends its session token to the package's intended ProAgentStore API for validation.
- The local artifact runtime handles selected source files within a run, and the Git helper invokes Git with a fixed argument list.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/local-artifact/runtime.jsView on unpkg · L22This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.96.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.96 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.