@docusaurus/plugin-content-pages
Pages plugin for Docusaurus.
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 | publisher-changed | AI (provenance): Docusaurus canary releases are published via GitHub Actions CI/CD by design. SLSA provenance attestation confirms the build originates from the official facebook/docusaurus repo. This pattern is stable for this package. | ai | |
| dependencies | unvetted-dep:webpack | AI (dependencies): webpack is a standard, widely-trusted build tool and a legitimate dependency for Docusaurus plugins; this finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): @docusaurus/core is a same-org monorepo sibling dependency; the phantom-dep finding is a false positive for this intra-monorepo package structure. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 8 / 0 | |
| 3.10.0 | 8 / 0 | |
| 3.9.2 | 8 / 0 | |
| 3.9.1 | 8 / 0 | |
| 3.9.0 | 8 / 0 | |
| 3.8.1 | 8 / 0 | |
| 3.8.0 | 8 / 0 | |
| 3.7.0 | 8 / 0 | |
| 3.6.3 | 8 / 0 | |
| 3.6.2 | 8 / 0 | |
| 3.6.1 | 8 / 0 | |
| 3.6.0 | 8 / 0 | |
| 3.5.2 | 8 / 0 | |
| 3.5.1 | 8 / 0 | |
| 3.5.0 | 8 / 0 | |
| 3.4.0 | 8 / 0 | |
| 3.3.2 | 8 / 0 | |
| 3.3.1 | 8 / 0 | |
| 3.3.0 | 8 / 0 | |
| 3.2.1 | 8 / 0 | |
| 3.2.0 | 8 / 0 | |
| 3.1.1 | 8 / 0 | |
| 3.1.0 | 8 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 | |
| 2.4.3 | 8 / 0 | |
| 2.4.1 | 8 / 0 | |
| 2.4.0 | 8 / 0 | |
| 2.3.1 | 8 / 0 | |
| 2.3.0 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.1 | 8 / 1 | |
| 2.0.0 | 8 / 1 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.