← Home

@sitespeed.io/geckodriver

npm Repository Homepage
3
Versions
—
License
Yes
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

toblisoulgalorebeenanner

Keywords

webdrivergeckodriverfirefox

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Legitimate maintenance release after dormancy; diff shows clean dependency refactor, no suspicious additions. ai
install-scripts install-script:install AI (install-scripts): install.js fetches geckodriver binary; standard pattern for this package across all versions. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used to launch geckodriver binary; core functionality of this package. ai

Versions (showing 3 of 3)

Version Deps Published
0.36.2 1 / 7
0.36.1 1 / 7
0.36.0 3 / 7

v0.36.2

1 finding
LOW No provenance attestation provenance

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

v0.36.1

1 finding
LOW No provenance attestation provenance

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

v0.36.0

2 findings
HIGH Package has 'install' script install-scripts

Script: node install.js

LOW No provenance attestation provenance

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