@proagentstore/cli@0.4.106
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The scanner’s process and network indicators correspond to user-invoked CLI features and package-aligned authentication and update checks.
Decision evidence
public snapshot- package.json contains build, development, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap checks for updates only when the user runs `up`; its lookup targets this package’s published version.
- The sign-in callback sends the session token to the configured ProAgentStore authentication endpoint for validation.
- The inspected process launches are tied to local runner, repository, and agent workflows; local artifact files are written under the run’s scratch directory.
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.106.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.106 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.