← Home

@tldraw/mermaid

npm Repository Homepage

Mermaid diagram to tldraw shape conversion.

4
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

tldraw-personalsteveruizokmimetldrawmitjatldrawsiobhantldraw

Keywords

tldrawmermaiddiagramcanvasinfinite

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): tldraw migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this package going forward. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers follow tldraw org naming convention; consistent with org-level CI publishing transition. ai
phantom-deps phantom-dep:@tldraw/tlschema AI (phantom-deps): Same-org dep used transitively via tldraw peer; stable false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
5.1.1 3 / 2
5.1.0 3 / 2
5.0.1 3 / 2
5.0.0 3 / 2

v5.1.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.1.0

2 findings
HIGH Publisher changed: tldraw-personal → GitHub Actions (on 2026-06-03) provenance

This version was published by a different npm account than previous versions on 2026-06-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.