registry / @extenshi/cli / 0.24.0
@extenshi/cli@0.24.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe postinstall hook sends limited install telemetry only after positive consent, and the reviewed runtime findings are tied to CLI functions. The scanner signals do not establish malicious behavior.
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; other reviewed behavior requires invoking the corresponding CLI command.
Impact
No concrete harmful effect was established from the inspected source.
Mechanism
The hook checks for positive telemetry consent before sending an install event. The inspected login, source verification, and screenshot code performs their named tasks.
AI rationale
The postinstall hook sends limited install telemetry only after positive consent, and the reviewed runtime findings are tied to CLI functions. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs a postinstall hook and exposes the CLI through dist/cli.js.
- The hook skips non-dependency installs and requires recorded positive telemetry consent before continuing.
- The telemetry payload contains an install event and coarse runtime details; the hook sends it by HTTPS.
- The login runtime binds its callback server to loopback, and source verification runs in a temporary clean room.
- Screenshots are an explicit CLI command that resolves Playwright for the requested task.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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 Critical5 High5 Medium8 Low
CriticalPrevious Version Dangerous Deltadist/screenshots.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.24.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.24.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.