← Home

edge-launcher

npm

Launcher for the Microsoft Edge browser.

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

andysterlandauchenberg

Keywords

edgediagnosticsdevtoolsbrowserspawnprocesslaunch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): The bundled Win32/MicrosoftEdgeLauncher.exe is the core artifact of this official Microsoft Edge launcher package; its presence is expected and legitimate across all versions. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance infrastructure; absence of attestation is expected for this long-established Microsoft-authored package. ai

Versions (showing 3 of 3)

Version Deps Published
1.2.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v1.2.2

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/x86/MicrosoftEdgeLauncher.exe

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • Win32/MicrosoftEdgeLauncher.exe

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.