@proagentstore/cli@0.4.133
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no concrete attack: the package has no install lifecycle hook, and the reviewed credential transfers go to the PAGS service or support coding-task repository access. The scanner’s shell and network signals are explained by these CLI features.
Decision evidence
public snapshot- package.json exposes the CLI binary and lists only build, development, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap checks for an update only when the user invokes `up`; the update installs another release of this CLI package.
- Login sends the session token to the fixed api.proagentstore.online service endpoint for validation.
- The site-builder runtime validates the broker URL against its PAGS broker prefix before sending the run token there.
- The coding runtime uses the supplied clone URL for repository cloning; the credential helper adds credentials only to HTTPS clone URLs.
- The scanner’s shell and network matches correspond to CLI update, authentication, site-builder, and coding features visible in source.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32This 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.133.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.133 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.