@proagentstore/cli@0.4.108
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 inspected runtime behavior matches the CLI's declared functions. Scanner signals for shell, environment, network, and child-process use were not evidence of an attack in the reviewed paths.
Decision evidence
public snapshot- The manifest points to a CLI entrypoint and lists build, development, and typecheck scripts; it declares no install lifecycle hook.
- The bootstrap updater runs only when the user invokes `up`, and the CLI then loads the selected payload.
- Login validates the returned session with the PAGS API; CLI requests send a PAGS token to the configured PAGS API base.
- Repository helpers run git checks in the selected directory and embed a token only in HTTPS clone URLs.
- Local artifact runs start from a validated task request; inspected code did not establish an unrelated credential transfer or harmful command execution.
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.108.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.108 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.