registry / @extenshi/cli / 0.26.0
@extenshi/cli@0.26.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The install-time telemetry requires positive recorded consent, and the flagged runtime operations are tied to explicit CLI features or local smoke-test observation.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installation runs the postinstall hook; CLI features run when the user invokes their commands.
Impact
No unconsented credential disclosure, destructive action, or hidden execution was established.
Mechanism
The hook sends limited telemetry only when prior consent is recorded and opt-out conditions permit it. Authenticated API calls use the configured service endpoint, while process execution supports browser login or explicit rebuild verification.
AI rationale
Source inspection found no malicious behavior. The install-time telemetry requires positive recorded consent, and the flagged runtime operations are tied to explicit CLI features or local smoke-test observation.
Evidence
scripts/postinstall.cjsdist/pay.jsdist/pay-test-cycle.jsdist/cli.jsdist/smoke.jsdist/login-runtime.jsdist/amo-source.jsdist/project.js
Network endpoints3
eu.i.posthog.combff.extenshi.io127.0.0.1
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook is gated on a real dependency install, positive recorded telemetry consent, and environment opt-outs; it sends an install event with coarse platform and version data.
- Payment commands send the configured service key to the configured service endpoint; callers invoke them through explicit commands, and mutations require an apply flag.
- The reported browser runtime operations collect extension errors for local smoke-test observations.
- Process launching is used to open a browser during login, while rebuild commands run only through the explicit clean-room verification option.
- The project client sends authenticated requests to the configured Extenshi backend.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
8 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 Medium8 Low
CriticalPrevious Version Dangerous Deltadist/project.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/login-runtime.js
HighShell
HighRuntime Package Installdist/amo-source.js
HighSemantic Analysis Limiteddist/cli.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
LowWeak Crypto
Affected versions and remediation
This report applies to @extenshi/cli@0.26.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.26.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.