@proagentstore/cli@0.4.125
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected runtime behavior supports the CLI’s stated functions. Scanner signals for shell, child processes, environment access, and networking correspond to explicit runner or repository operations; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json lists build, dev, and typecheck scripts, with no install lifecycle hook.
- Bootstrap checks for updates only when the user invokes `up`; the payload lookup accepts packages named @proagentstore/cli.
- The CLI uses the ProAgentStore API by default and supports explicit API and runner URL configuration.
- Local artifact generation writes generated résumé and cover letter files to its output directory.
- Repository operations use git for the selected repository and clone URL.
- The shell restart path runs the configured restart command as part of runner restart behavior.
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.125.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.125 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.