registry / @extenshi/cli / 0.23.1
@extenshi/cli@0.23.1
Pre-publish security scanner for browser extensions
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe package has a postinstall telemetry hook, but it requires previously recorded positive consent and sends limited install metadata. The flagged runtime process and package-install references are used for browser login, generated instructions, or explicit screenshot setup; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation may run the postinstall hook; CLI telemetry and browser launch occur when the user runs commands.
Impact
No confirmed harmful effect or attack surface was established in the inspected source.
Mechanism
The hook checks for recorded consent before sending install metadata; reviewed shell-related references either print build instructions or launch the browser for login.
AI rationale
The package has a postinstall telemetry hook, but it requires previously recorded positive consent and sends limited install metadata. The flagged runtime process and package-install references are used for browser login, generated instructions, or explicit screenshot setup; no concrete attack behavior was found.
Evidence
scripts/postinstall.cjs
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall hook that leads to the inspected telemetry script.
- The postinstall exits unless the user has already recorded telemetry consent; it sends install metadata to the configured PostHog host.
- The CLI asks for telemetry consent before recording command events.
- Browser launching uses platform browser commands with the login URL as an argument.
- The AMO source command generates build instructions; the npm install string is output text, not executed here.
- Screenshot support resolves Playwright and describes a user-run install command; no install is performed at import.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsTelemetryUrlStrings
NoLicense
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 Critical4 High5 Medium8 Low
CriticalPrevious Version Dangerous Deltadist/screenshots.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/login-runtime.js
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 Cryptodist/evidence-ingest.js
Affected versions and remediation
This report applies to @extenshi/cli@0.23.1.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.23.1 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.