@appium/base-driver
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): Transition from human publisher (jlipps) to GitHub Actions CI/CD with SLSA provenance. Standard modernization for the Appium project. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer list change in a large, well-established project (Appium). Not indicative of takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package; parent appium/appium repo is active. Individual packages release only when their code changes. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used to compile a developer-controlled HTTP log format string into a formatter function — a standard logging middleware pattern, not a runtime injection risk. | ai | |
| dependencies | unvetted-dep:http-status-codes | AI (dependencies): Widely-used, well-known HTTP status code utility library with no known security issues. | ai | |
| dependencies | unvetted-dep:@appium/types | AI (dependencies): First-party Appium package from the same monorepo; legitimate and well-maintained. | ai | |
| dependencies | unvetted-dep:@appium/support | AI (dependencies): First-party Appium package from the same monorepo; legitimate and well-maintained. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 10.6.0 | 16 / 0 | |
| 10.5.2 | 18 / 0 | |
| 10.5.1 | 18 / 0 | |
| 10.5.0 | 18 / 0 | |
| 10.4.0 | 18 / 0 | |
| 10.3.0 | 18 / 0 | |
| 10.2.2 | 18 / 0 | |
| 10.2.1 | 18 / 0 | |
| 10.2.0 | 18 / 0 | |
| 10.1.2 | 19 / 0 | |
| 10.1.1 | 19 / 0 | |
| 10.1.0 | 19 / 0 | |
| 10.0.1 | 19 / 0 | |
| 10.0.0 | 19 / 0 |
v10.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. 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.
v10.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-08. 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.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.