registry / @extenshi/cli / 0.34.0
@extenshi/cli@0.34.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found a consent-gated install telemetry event and caller-invoked CLI requests to the package's service endpoints. The flagged execution, network, and dynamic-code primitives fit the CLI's documented workflows, and no concrete attack behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs the postinstall hook; it exits unless the package is installed under node_modules and telemetry is recorded as true.
Impact
The inspected behavior supports opted-in telemetry and the CLI's stated service operations; no credential theft, unrequested account action, or other attack was established.
Mechanism
The hook sends package version, Node version, operating system, architecture, and an anonymous install identifier to the telemetry collector. Runtime API calls use the CLI's configured Extenshi endpoints and are tied to invoked commands.
AI rationale
Source inspection found a consent-gated install telemetry event and caller-invoked CLI requests to the package's service endpoints. The flagged execution, network, and dynamic-code primitives fit the CLI's documented workflows, and no concrete attack behavior was identified.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI sends API keys through invoked workflows to Extenshi service endpoints and uses credentials for the requested catalog, project, scan, and Pay operations.
- The postinstall hook requires a stored telemetry acceptance and sends anonymous package and runtime metadata; the CLI asks for a choice and supports opt-outs.
- The included publisher and contract dependencies expose their stated library functions and do not define install hooks.
- The remaining inspected modules perform local scanning, listing checks, localization, screenshot, report, and asset-rendering tasks; no attack behavior was identified.
Evidence against
- The postinstall hook sends an install event, but its stored-consent gate and opt-out checks make that reporting package-aligned telemetry rather than an unconsented installation beacon.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/login-runtime.jsView file
11*/
L12: import { spawn } from 'node:child_process';
L13: import http from 'node:http';
High
Child Process
Package source references child process execution.
dist/login-runtime.jsView on unpkg · L11Findings
1 Critical5 High5 Medium9 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/login-runtime.js
HighShell
HighRuntime Package Installdist/amo-source.js
HighSemantic Analysis Limiteddist/controls.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/screenshots.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvaldist/controls.js
Affected versions and remediation
This report applies to @extenshi/cli@0.34.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.34.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.