@proagentstore/cli@0.4.166
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged process, network, and filesystem operations are associated with user-invoked CLI and runner features, including scoped push protection.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and lists build, dev, and typecheck scripts; it has no lifecycle hook.
- dist/index.js uses the service API for session validation and runner management.
- The site builder starts a configured engine in its run directory and reports worker events.
- The Actions runner downloads and configures a GitHub runner when its install operation is invoked.
- Repository inspection runs a read-only git status query in the requested work directory.
- The push guard installs scoped git transport wrappers, while coding runtime confines work directories.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32Package source references shell execution.
dist/browser-runner/coding/actions-runner.jsView on unpkg · L138Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.166.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.166 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.