registry / @extenshi/cli
@extenshi/cli
Pre-publish security scanner for browser extensions
This report shows the evidence for @extenshi/cli@0.44.0. 0 of 33 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe postinstall hook is gated on recorded telemetry consent and reports limited adoption data to PostHog. The flagged process execution and network activity serve explicit CLI features; the reviewed sources show no malicious data flow or automatic unrelated execution.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation can trigger the postinstall hook, but it sends only when telemetry is already enabled in the user's Extenshi config. Product commands run when invoked.
Impact
No unconsented collection of credentials or project data, unrelated execution, or other attack behavior was identified.
Mechanism
The hook posts an anonymous install event to PostHog. Other process and network activity supports the CLI's scanner, project setup, and publishing features.
AI rationale
The postinstall hook is gated on recorded telemetry consent and reports limited adoption data to PostHog. The flagged process execution and network activity serve explicit CLI features; the reviewed sources show no malicious data flow or automatic unrelated execution.
Evidence
~/.extenshi/config.jsonproject files explicitly targeted by `extenshi analytics init`
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
- The postinstall telemetry ping exits unless the user has previously recorded telemetry consent.
- The install event contains package surface and version, Node version, platform, architecture, and an anonymous ID.
- The install ping is sent to the configured PostHog ingestion host; no host, username, path, or project data appears in its payload.
- CLI runtime telemetry is disclosed as asking a first-run question and can be disabled.
Evidence against
- The package declares a postinstall hook that runs during installation.
- The CLI uses child processes for Git and for explicitly requested project setup or verification commands.
- The package performs network requests for its scanning, publishing, analytics, and account features.
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/build-map-store.jsView file
28*/
L29: import { execFile } from 'node:child_process';
L30: import { randomUUID } from 'node:crypto';
High
Child Process
Package source references child process execution.
dist/build-map-store.jsView on unpkg · L28Findings
7 High5 Medium9 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/build-map-store.js
HighShelldist/analytics-init.js
HighSame File Env Network Executiondist/analytics-init.js#virtual:normalized:round1
HighCross File Remote Execution Contextdist/build-map.js
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
Low
Affected versions and remediation
This report applies to @extenshi/cli@0.44.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @extenshi/cli@0.44.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.