@proagentstore/cli@0.4.107
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or runtime self-dependency, and the flagged execution paths align with explicit CLI update and runner functions. The static scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the CLI through dist/bootstrap.js and defines build, dev, and typecheck scripts, with no install lifecycle hook or runtime self-dependency.
- The bootstrap checks for updates only when the user runs the up command.
- The update helper queries npm for this package and installs that same package into a private cache directory.
- Runner restart shell execution uses the explicitly configured PAGS_RESTART_COMMAND environment value.
- The local artifact runtime builds a task-specific engine command and refuses runs where a provider API key would reach the CLI.
- Repository process calls support work directory checks, cloning, and SSH identity probes.
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.107.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.107 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.