@proagentstore/cli@0.4.95
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged shell and process execution are part of user-configured runner restart, repository, or local task functions. Inspected credential and network use is directed to the package service or a caller-supplied repository destination; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json declares the command-line entry point and only build, development, and type-check scripts; it has no install lifecycle hook.
- The bootstrap checks for updates only when the user runs the runner command and loads the selected bundled or cached package payload.
- Saved login sessions are sent to the package's ProAgentStore API host for authentication validation.
- Local artifact tasks validate their input, read selected workspace files, write under the workspace applications directory, and launch a configured local CLI.
- Repository cloning requires a supplied work directory and clone URL; it uses fixed git arguments and adds a supplied token only to HTTPS clone URLs.
- The shell restart path requires a configured restart command and runs as part of runner restart handling.
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.95.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.95 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.