safaridriver
An NPM wrapper for handling the Safaridriver binary.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from wdio-user to GitHub Actions as part of a documented CI/CD migration; SLSA provenance attestation confirms the artifact was built from the official webdriverio-community repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is expected for a macOS Safari WebDriver wrapper; the resumed publish is backed by SLSA provenance attestation from the official GitHub org, ruling out account takeover. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 0 / 9 | |
| 1.0.0 | 0 / 12 | |
| 0.1.2 | 0 / 12 | |
| 0.1.1 | 0 / 11 | |
| 0.1.0 | 0 / 11 | |
| 0.0.6 | 0 / 11 | |
| 0.0.5 | 0 / 11 | |
| 0.0.4 | 0 / 11 | |
| 0.0.3 | 0 / 11 | |
| 0.0.2 | 0 / 11 | |
| 0.0.1 | 0 / 1 |
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.