@docusaurus/faster
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of facebook/docusaurus monorepo; minimal README is intentional for a utility sub-package. | ai | |
| phantom-deps | phantom-dep:webpack | AI (phantom-deps): webpack is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 10 / 0 | |
| 3.10.0 | 10 / 0 | |
| 3.9.2 | 9 / 0 | |
| 3.9.1 | 9 / 0 | |
| 3.9.0 | 9 / 0 | |
| 3.8.1 | 9 / 0 | |
| 3.8.0 | 9 / 0 | |
| 3.7.0 | 9 / 0 | |
| 3.6.3 | 9 / 0 | |
| 3.6.2 | 9 / 0 | |
| 3.6.1 | 9 / 0 | |
| 3.6.0 | 8 / 0 | |
| 3.5.2 | 7 / 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.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.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.