@proagentstore/cli@0.4.116
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 the inspected execution paths are user-invoked CLI and runner features. Network access is to the package's service API, and the flagged process execution is bounded to configured tooling; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json lists build, dev, and typecheck scripts; the package is exposed as a CLI, with no install lifecycle script in the inspected manifest.
- dist/index.js registers user-facing CLI commands, and `pags up` sends the saved session token to the ProAgentStore API to fetch the user's instances.
- The bootstrap only checks for updates when the user invokes `up`; it installs a requested release of this same package into its cache.
- The local artifact runtime launches a configured engine in a scratch directory and pauses if it detects a provider API key; Codex runs with read-only sandbox settings.
- The repository helper reuses existing checkouts and refuses to clone into a non-empty directory unless it is the owner's selected folder.
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.116.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.116 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.