@extenshi/cli@0.33.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall telemetry is guarded by recorded affirmative consent and opt-out checks, and sends limited package-aligned adoption data. The scanner’s execution and network indicators correspond to the CLI’s documented functions; the inspected source did not establish malicious behavior.
Decision evidence
public snapshot- package.json runs scripts/postinstall.cjs during installation, and the script sends an installation event only when the existing config explicitly has telemetry set to true; it also honors opt-out variables and skips CI and workspace installs.
- The install event goes to the Extenshi PostHog collector and contains an anonymous install ID plus package and runtime metadata; no credentials or package contents are included in the request.
- The inspected runtime and dependency entrypoints support the stated CLI, browser testing, publishing, and rendering functions; no concrete attack behavior was identified.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/login-runtime.jsView on unpkg · L11Findings
Affected versions and remediation
This report applies to @extenshi/cli@0.33.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.33.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.