@apify/docs-theme
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 | missing-githead | AI (provenance): CI-published Apify package; gitHead gaps are benign for this automated publish flow. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Frequent automated releases are normal for this actively maintained docs-theme package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 251 versions; missing description is metadata gap, not malware signal. | ai | |
| phantom-deps | phantom-dep:prism-react-renderer | AI (phantom-deps): Config-file reference; stable pattern for build tools. | ai | |
| phantom-deps | phantom-dep:docusaurus-gtm-plugin | AI (phantom-deps): Config-file reference; stable pattern for build tools. | ai | |
| phantom-deps | phantom-dep:@stackql/docusaurus-plugin-hubspot | AI (phantom-deps): Config-file reference; stable pattern for build tools. | ai | |
| phantom-deps | phantom-dep:react-hotkeys-hook | AI (phantom-deps): Config-file reference; stable pattern for build tools. | ai | |
| phantom-deps | phantom-dep:babel-loader | AI (phantom-deps): Config-file reference; stable pattern for build tools. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.0.265 | 16 / 0 | |
| 1.0.264 | 16 / 0 | |
| 1.0.263 | 16 / 0 | |
| 1.0.262 | 16 / 0 | |
| 1.0.261 | 16 / 0 | |
| 1.0.260 | 16 / 0 | |
| 1.0.259 | 16 / 0 | |
| 1.0.258 | 16 / 0 | |
| 1.0.257 | 16 / 0 | |
| 1.0.256 | 16 / 0 | |
| 1.0.255 | 16 / 0 | |
| 1.0.254 | 16 / 0 | |
| 1.0.253 | 16 / 0 | |
| 1.0.252 | 16 / 0 | |
| 1.0.251 | 16 / 0 | |
| 1.0.250 | 16 / 0 | |
| 1.0.245 | 17 / 0 | |
| 1.0.243 | 17 / 0 | |
| 1.0.239 | 17 / 0 | |
| 1.0.238 | 17 / 0 | |
| 1.0.237 | 17 / 0 | |
| 1.0.235 | 17 / 0 | |
| 1.0.234 | 17 / 0 | |
| 1.0.233 | 17 / 0 | |
| 1.0.232 | 17 / 0 | |
| 1.0.231 | 17 / 0 | |
| 1.0.228 | 17 / 0 | |
| 1.0.227 | 17 / 0 | |
| 1.0.225 | 17 / 0 | |
| 1.0.224 | 17 / 0 |
v1.0.265
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.264
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.263
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.262
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.261
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.260
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.259
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.258
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.257
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.256
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.255
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.254
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.253
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.