@accio-ai/ecommerce-cli@0.5.0
Local, statically compiled ecommerce automation toolkit
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe launcher sends limited failure telemetry to a loopback gateway, despite the README stating that the package does not use telemetry or remote services. The destination restriction and narrow payload reduce risk, but the undisclosed runtime reporting warrants a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
A qualifying business command fails while the gateway token and valid trace context are present; telemetry has not been disabled.
Impact
Failure and correlation metadata may be reported to the local gateway without disclosure in the README.
Mechanism
The launcher POSTs trace identifiers and limited failure metadata with Basic authorization to a loopback gateway.
AI rationale
The launcher sends limited failure telemetry to a loopback gateway, despite the README stating that the package does not use telemetry or remote services. The destination restriction and narrow payload reduce risk, but the undisclosed runtime reporting warrants a warning.
Evidence
README.mdlauncher-diagnostics.cjsbin/ecomctl.cjs
Network endpoints3
127.0.0.1:4097/tracelocalhost/traceuser-configured loopback HTTP(S) gateway ending in /trace
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The README says the package does not use telemetry or remote services, but the launcher sends failure diagnostics.
- Diagnostics run for qualifying business-command failures unless telemetry is disabled, and require a gateway token and trace context.
- The event includes trace identifiers, timing, platform, architecture, version and error details.
- The destination is restricted to loopback, defaulting to http://127.0.0.1:4097/trace.
Evidence against
- The diagnostic request is gated on a failed command, a token and valid trace context; telemetry can be disabled with ECOMCTL_TELEMETRY_DISABLED.
- The payload contains no command input or output, and the code checks that it does not include the token.
- The postinstall hook verifies the binary checksum and runs best-effort local database initialization.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
UrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = node postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgREADME.mdView file
7The platform package contains one statically compiled binary; this main package contains only the Node.js launcher, the shared target manifest, install checksum verification, README, and changelog. After checksum verification, `postinstall`
Medium
Ai Review Evidence
The README says the package does not use telemetry or remote services, but the launcher sends failure diagnostics.
Findings
1 High7 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumAi Review EvidenceREADME.md
MediumAi Review Evidencelauncher-diagnostics.cjs
MediumAi Review Evidencelauncher-diagnostics.cjs
MediumAi Review Evidencelauncher-diagnostics.cjs
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @accio-ai/ecommerce-cli@0.5.0.
See all versions of @accio-ai/ecommerce-cli for other recorded verdicts.
- Review the evidence and your use of @accio-ai/ecommerce-cli@0.5.0 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.