← Home

tldraw

npm Repository Homepage
37
Versions
—
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

tldrawsdkdrawingappdevelopmentwhiteboardcanvasinfinite

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 37 of 37)

Version Deps Published
5.2.5 14 / 13
5.2.4 14 / 13
5.2.3 14 / 13
5.2.2 14 / 13
5.2.1 14 / 13
5.2.0 14 / 13
5.1.1 14 / 13
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.5.3 14 / 13
4.5.2 14 / 13
4.5.1 14 / 13
4.5.0 14 / 13
4.4.2 14 / 13
4.4.1 14 / 13
4.4.0 14 / 13
4.3.3 14 / 13
4.3.2 14 / 13
4.3.1 14 / 13
4.3.0 14 / 13
4.2.4 14 / 11
4.2.3 14 / 11
4.2.2 14 / 13
4.2.1 14 / 11
4.2.0 14 / 11
4.1.3 14 / 11
4.0.5 14 / 11
3.15.6 14 / 13

v5.2.5

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.2.4

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.2.3

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.2.2

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.2.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.2.0

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.

v4.5.3

1 finding
LOW No provenance attestation provenance

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

v4.5.2

1 finding
LOW No provenance attestation provenance

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

v4.5.1

1 finding
LOW No provenance attestation provenance

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

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.4.1

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.2

1 finding
LOW No provenance attestation provenance

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

v4.3.1

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.3

1 finding
LOW No provenance attestation provenance

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

v4.2.2

1 finding
LOW No provenance attestation provenance

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

v4.2.1

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.

v4.2.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.

v3.15.6

1 finding
LOW No provenance attestation provenance

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