registry / @extenshi/cli / 0.15.2
@extenshi/cli@0.15.2
Pre-publish security scanner for browser extensions
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a postinstall telemetry ping, but it is skipped without previously saved positive consent and contains no credential or project-file harvesting. Other network, file, and process operations are aligned with explicit scanner, publishing, reporting, and login commands.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install after prior telemetry consent, or explicit CLI scan/login commands
Impact
Writes Extenshi local configuration and sends limited telemetry only after recorded consent; explicit scans upload the selected artifact to the configured scan API.
Mechanism
consent-gated telemetry and user-invoked extension scanning
AI rationale
Source inspection confirms a postinstall telemetry ping, but it is skipped without previously saved positive consent and contains no credential or project-file harvesting. Other network, file, and process operations are aligned with explicit scanner, publishing, reporting, and login commands.
Evidence
package.jsonscripts/postinstall.cjsdist/scan.jsdist/telemetry-consent.jsdist/login-runtime.js~/.extenshi/config.json
Network endpoints4
eu.i.posthog.comregistry.npmjs.org/@extenshi/cli/latestscan.extenshi.iobff.extenshi.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- postinstall exists and can send an install event.
- Postinstall reads and may update ~/.extenshi/config.json.
Evidence against
- Postinstall exits unless telemetry was previously recorded true.
- Install payload is limited to anonymous telemetry and coarse platform/version fields.
- Artifact upload occurs only through the explicit scan command.
- Browser launch and loopback listener are explicit login flow behavior.
- No hidden shell execution, remote code loading, credential exfiltration, or AI-agent config writes found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
NoLicense
Source & flagged code
5 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/review-checks.jsView file
252// A pre-publish "will the store reject this?" gate must only flag what the
L253: // developer can act on AND what the store actually rejects. eval()/new Function()
L254: // and dynamic-<script> patterns inside a bundled third-party library (webpack
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/review-checks.jsFindings
2 High5 Medium8 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltadist/cli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/auto-update.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvaldist/review-checks.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @extenshi/cli@0.15.2.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.15.2 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.