@docusaurus/preset-classic
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): Same-org peer/transitive dep; phantom-dep heuristic is a stable false positive for this preset package. | ai | |
| phantom-deps | phantom-dep:@docusaurus/plugin-css-cascade-layers | AI (phantom-deps): Same-org dep declared for re-export; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 15 / 0 | |
| 3.10.0 | 15 / 0 | |
| 3.9.2 | 15 / 0 | |
| 3.9.1 | 15 / 0 | |
| 3.9.0 | 15 / 0 | |
| 3.8.1 | 15 / 0 | |
| 3.8.0 | 15 / 0 |
v3.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.