appium
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): Appium migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected publisher for this org-managed package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large monorepo package; file count growth across minor versions is normal for appium. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Appium is a large project with multiple maintainers; team changes are routine and jlipps is the canonical long-term maintainer. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Appium's documented extension auto-install; runs a local script, not remote code. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Referenced in config/build tooling, not directly imported at runtime; stable false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in extension schema-loading path; expected plugin infrastructure for Appium. | ai | |
| phantom-deps | phantom-dep:@appium/docutils | AI (phantom-deps): Used in build/docs scripts, not runtime imports; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.4.2 | 25 / 0 | |
| 3.3.1 | 25 / 0 | |
| 3.3.0 | 26 / 0 | |
| 3.2.2 | 26 / 0 | |
| 3.2.1 | 26 / 0 | |
| 3.2.0 | 26 / 0 | |
| 3.1.1 | 29 / 0 | |
| 3.0.2 | 29 / 0 | |
| 3.0.1 | 29 / 0 | |
| 3.0.0 | 29 / 0 |
v3.4.2
2 findingsScript: node ./scripts/autoinstall-extensions.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
2 findingsScript: node ./scripts/autoinstall-extensions.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.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.
v3.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.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsScript: node ./scripts/autoinstall-extensions.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.