@docusaurus/theme-mermaid
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:tslib | AI (phantom-deps): tslib is a known implicit dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): Same-org scope dependency; stable for Docusaurus packages. | ai | |
| phantom-deps | phantom-dep:@docusaurus/module-type-aliases | AI (phantom-deps): Same-org scope dependency; stable for Docusaurus packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 7 / 0 | |
| 3.10.0 | 7 / 0 | |
| 3.9.2 | 7 / 1 | |
| 3.9.1 | 7 / 1 | |
| 3.9.0 | 7 / 1 | |
| 3.8.1 | 7 / 1 | |
| 3.8.0 | 7 / 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.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.