@appium/docutils
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 monorepo publishes via GitHub Actions CI; jlipps→GHA transition is expected for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA attestation confirms legitimate CI publish; dormancy explained by infrequent docutils releases. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): package-directory is a well-known, benign npm utility; no malicious indicators. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.4.2 | 12 / 0 | |
| 2.4.1 | 12 / 0 | |
| 2.4.0 | 12 / 0 | |
| 2.3.1 | 12 / 0 | |
| 2.3.0 | 12 / 0 | |
| 2.2.2 | 12 / 0 | |
| 2.2.1 | 12 / 0 | |
| 2.2.0 | 14 / 0 | |
| 2.1.2 | 14 / 0 | |
| 2.1.1 | 14 / 0 | |
| 2.1.0 | 14 / 0 | |
| 2.0.1 | 14 / 0 | |
| 2.0.0 | 14 / 0 |
v2.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
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.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.