tldraw
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration from personal npm account to GitHub Actions CI/CD with SLSA provenance. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): tldraw uses a custom license file; stable across versions. | ai | |
| phantom-deps | phantom-dep:@tldraw/driver | AI (phantom-deps): First-party tldraw scoped dep; re-exported rather than directly imported is normal for this monorepo structure. | ai | |
| phantom-deps | phantom-dep:idb | AI (phantom-deps): idb is a declared runtime dep; phantom-dep fires due to indirect import pattern in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-list | AI (phantom-deps): Declared runtime dep; phantom-dep fires due to indirect import pattern in this monorepo package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 14 / 13 | |
| 5.0.1 | 14 / 13 | |
| 5.0.0 | 14 / 13 | |
| 4.5.12 | 14 / 13 | |
| 4.5.10 | 14 / 13 | |
| 4.5.9 | 14 / 13 | |
| 4.5.8 | 14 / 13 | |
| 4.5.7 | 14 / 13 | |
| 4.5.6 | 14 / 13 | |
| 4.5.5 | 14 / 13 | |
| 4.5.4 | 14 / 13 | |
| 4.4.2 | 14 / 13 | |
| 4.3.3 | 14 / 13 | |
| 4.2.4 | 14 / 11 | |
| 4.1.3 | 14 / 11 | |
| 4.0.5 | 14 / 11 |
v5.1.0
2 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.