@extenshi/cli@0.38.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI’s consent flow skips CI, but the telemetry path still defaults to enabled when no saved opt-out or disabling environment variable exists. The reported fields are limited, and the install hook itself requires recorded consent, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A CLI command runs without a saved telemetry=false preference or telemetry opt-out; the consent prompt is skipped in CI, and the command proceeds to emit telemetry.
Impact
Usage telemetry leaves the machine before an unattended user has been asked to consent. The inspected event fields do not include flag values.
Mechanism
The CLI sends command usage events through PostHog to https://eu.i.posthog.com. Events include the command and flag names.
AI rationale
The CLI’s consent flow skips CI, but the telemetry path still defaults to enabled when no saved opt-out or disabling environment variable exists. The reported fields are limited, and the install hook itself requires recorded consent, so this warrants a warning rather than a block.
Evidence
dist/telemetry-consent.jsdist/telemetry.jsdist/command-lifecycle.js~/.extenshi/config.json
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Each CLI command attempts to ask for telemetry consent, then emits a command-start event.
- The consent question is skipped in CI, while telemetry remains enabled unless an opt-out or saved false preference is present.
- The emitted command event includes the command and flag names; the configured analytics host is PostHog EU.
- The install hook sends telemetry only when config already records telemetry: true.
Evidence against
- Interactive users are told what runtime telemetry reports and how to disable it.
- The install hook requires recorded consent and its payload contains package/runtime details and an anonymous install ID.
- API calls use credentials for Extenshi services in response to explicit CLI operations.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
11 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 Critical6 High5 Medium9 Low
CriticalPrevious Version Dangerous Deltadist/analytics-init.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/login-runtime.js
HighShelldist/analytics-init.js
HighSame File Env Network Executiondist/analytics-init.js#virtual:normalized:round1
HighRuntime Package Installdist/amo-source.js
HighSemantic Analysis Limiteddist/analytics-init.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/screenshots.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @extenshi/cli@0.38.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.38.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.