@mermaid-js/mermaid-cli
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:@mermaid-js/layout-elk | AI (phantom-deps): Same-org scoped dep bundled into dist; not directly imported in source but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@mermaid-js/mermaid-zenuml | AI (phantom-deps): Same-org scoped dep; bundled/optional usage pattern, stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established high-download package; absence of provenance is common and not a risk indicator here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 11.14.0 | 6 / 9 | |
| 11.12.0 | 5 / 10 | |
| 11.10.1 | 5 / 10 | |
| 11.9.0 | 5 / 10 | |
| 11.6.0 | 5 / 10 | |
| 11.4.3 | 5 / 10 |
v11.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.