@proagentstore/cli@0.4.110
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and inspected runtime behavior is consistent with CLI functions, intended-service authentication, and user-invoked updates. The scanner signals do not establish harmful behavior in source.
Decision evidence
public snapshot- package.json maps the CLI command to its bundled bootstrap and payload; it declares no lifecycle scripts.
- Local artifact source files are restricted to the workspace, and paths into generated applications are refused.
- Login sends the received session to the ProAgentStore API for session validation.
- The flagged repository helper runs a bounded git status query in the requested work directory.
- Self-update checking is gated on the user invoking the `up` command.
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.110.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.110 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.