@proagentstore/cli@0.4.99
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or confirmed attack behavior. The flagged shell, subprocess, and network calls support CLI updates, configured restarts, runner tasks, git diagnostics, and authentication.
Decision evidence
public snapshot- package.json lists build, development, and typecheck scripts; no install lifecycle script is present.
- The bootstrap gates its update check behind an argument check, a source checkout check, and a disable setting.
- Login sends the session token to the ProAgentStore API to validate it before saving the session.
- Runner requests require a token, and local artifact generation reads configured workspace files and launches local tools with constrained settings.
- Repository inspection runs a fixed git worktree check with fixed arguments.
- The restart shell command is used only when a restart command is configured in the environment.
- Static hints flag shell execution, subprocesses, environment access, and network use; inspected source ties these to runner, git, authentication, update, and configured restart functions.
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.99.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.99 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.