@proagentstore/cli@0.4.123
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 the inspected shell and network behavior is tied to CLI or runner functionality. The scanner signals did not establish a concrete attack surface.
Decision evidence
public snapshot- The manifest exposes a CLI and lists only build, development, and type-check scripts; it has no install lifecycle script.
- The local artifact runtime validates its inputs, excludes generated output from source inputs, and runs the selected engine with API-key refusal checks.
- The CLI registers user-facing commands, including login; login opens a local callback for sign-in.
- Repository helpers inspect and clone workdirs, while leaving a non-empty owner directory untouched.
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.123.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.123 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.