@apify/docs-search-modal
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package publishes via GitHub Actions with SLSA attestation; this is the expected CI/CD pattern for Apify org packages. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): styled-components is a declared runtime dependency used via config/theme; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 8 / 8 | |
| 1.3.6 | 8 / 8 | |
| 1.3.5 | 8 / 8 | |
| 1.3.3 | 8 / 8 | |
| 1.3.2 | 8 / 8 | |
| 1.3.1 | 8 / 8 | |
| 1.3.0 | 8 / 8 | |
| 1.2.3 | 8 / 8 | |
| 1.2.2 | 8 / 8 | |
| 1.2.1 | 8 / 8 | |
| 1.2.0 | 7 / 8 | |
| 1.1.1 | 7 / 8 | |
| 1.1.0 | 7 / 8 | |
| 1.0.26 | 7 / 8 |
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.