appium-xcode
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@appium/support | AI (dependencies): @appium/support is a first-party Appium organization package; it is a stable dependency of appium-xcode across versions and poses no supply chain risk. | ai | |
| phantom-deps | phantom-dep:plist | AI (phantom-deps): plist is explicitly declared in package.json dependencies; the phantom-dep finding is a false positive — it may be used in build output rather than directly imported in source. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 6.2.2 | 4 / 18 | |
| 6.2.1 | 4 / 15 | |
| 6.2.0 | 4 / 15 | |
| 6.1.10 | 7 / 17 | |
| 6.1.9 | 7 / 17 | |
| 6.1.8 | 7 / 17 | |
| 6.1.7 | 7 / 17 | |
| 6.1.6 | 7 / 17 | |
| 6.1.5 | 7 / 18 | |
| 6.1.4 | 7 / 18 | |
| 6.1.3 | 8 / 18 | |
| 6.1.2 | 8 / 18 | |
| 6.1.1 | 8 / 18 | |
| 6.1.0 | 8 / 18 | |
| 6.0.2 | 8 / 18 | |
| 6.0.1 | 8 / 18 | |
| 6.0.0 | 8 / 18 |
v6.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.