registry / @proagentstore/cli / 0.4.128
@proagentstore/cli@0.4.128
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged execution and network behavior supports CLI updates, device checks, PAGS API access, and requested repository cloning.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs a CLI command such as `pags up`, requests native preflight, or starts a coding session that needs a repository clone.
Impact
No malicious effect was established in the inspected source.
Mechanism
Updates are checked for `pags up`; preflight runs fixed probes, and service or repository credentials are used for their associated requests.
AI rationale
Source inspection found no install lifecycle hook or concrete attack behavior. The flagged execution and network behavior supports CLI updates, device checks, PAGS API access, and requested repository cloning.
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists build, dev, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap checks for a newer payload when the user runs `pags up`; it does not update on ordinary invocation.
- Native preflight runs fixed version and device probes, including `maestro --version`, `adb devices -l`, and `xcrun simctl` device listing.
- PAGS API requests send the supplied PAGS token to the configured API base, which defaults to `https://api.proagentstore.online`.
- For private repository cloning, the cloud supplies a token that is used with the clone URL; the coding CLI then runs in that repository.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/browser-runner/native/preflight.jsView file
17*/
L18: import { execFile } from "node:child_process";
L19: import { arch as osArch, platform as osPlatform } from "node:os";
High
Child Process
Package source references child process execution.
dist/browser-runner/native/preflight.jsView on unpkg · L17dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @proagentstore/cli@0.4.50
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.50
similarity = 0.462
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkg1364if (restarter === "command") {
L1365: deps.spawn(process.env[RESTART_COMMAND_ENV], { shell: true, detached: true, stdio: "ignore", env: process.env }).unref();
L1366: deps.exit(0);
Findings
1 Critical5 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/browser-runner/native/preflight.js
HighShelldist/index.js
HighSame File Env Network Executiondist/index.js
HighCommand Output Exfiltrationdist/index.js
HighSemantic Analysis Limiteddist/browser-runner/coding/repo.js#virtual:normalized:round1
MediumDynamic Requiredist/browser-runner/coding/runtime.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.128.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.128 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.