@tldraw/editor
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): tldraw uses a custom license file; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@types/core-js | AI (dependencies): @types/core-js is a stable DefinitelyTyped package; benign for this package. | ai | |
| phantom-deps | phantom-dep:@types/core-js | AI (phantom-deps): Types package used as runtime dep for polyfill conventions; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:is-plain-object | AI (phantom-deps): is-plain-object is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 5.2.5 | 14 / 15 | |
| 5.2.4 | 14 / 15 | |
| 5.2.3 | 14 / 15 | |
| 5.2.2 | 14 / 15 | |
| 5.2.1 | 14 / 15 | |
| 5.2.0 | 14 / 15 | |
| 5.1.1 | 14 / 15 | |
| 5.1.0 | 14 / 15 | |
| 5.0.1 | 14 / 15 | |
| 5.0.0 | 14 / 15 | |
| 4.5.12 | 15 / 15 | |
| 4.5.10 | 15 / 15 | |
| 4.5.9 | 15 / 15 | |
| 4.5.8 | 15 / 15 | |
| 4.5.7 | 15 / 15 | |
| 4.5.6 | 15 / 15 | |
| 4.5.5 | 15 / 15 | |
| 4.5.4 | 15 / 15 | |
| 4.5.3 | 15 / 15 | |
| 4.5.2 | 15 / 15 | |
| 4.5.1 | 15 / 15 | |
| 4.5.0 | 15 / 15 | |
| 4.4.2 | 15 / 15 | |
| 4.4.1 | 15 / 15 | |
| 4.4.0 | 15 / 15 | |
| 4.3.3 | 16 / 14 | |
| 4.3.2 | 16 / 14 | |
| 4.3.1 | 16 / 14 | |
| 4.3.0 | 16 / 14 | |
| 4.2.4 | 16 / 12 | |
| 4.2.3 | 16 / 12 | |
| 4.2.2 | 16 / 14 | |
| 4.2.1 | 16 / 12 | |
| 4.2.0 | 16 / 12 | |
| 4.1.3 | 16 / 12 | |
| 4.0.5 | 16 / 12 | |
| 3.15.6 | 16 / 14 |
v5.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.