@kitschpatrol/vite-plugin-tldraw
Vite plugin enabling module-like import of local tldraw .tldr files with automatic conversion to SVG or PNG.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kitschpatrol/tldraw-cli | AI (dependencies): Same-author dependency integral to this plugin's function; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 7 / 13 | |
| 5.1.6 | 7 / 13 | |
| 5.1.5 | 7 / 12 | |
| 5.1.4 | 7 / 12 | |
| 5.1.3 | 7 / 11 | |
| 5.1.2 | 7 / 11 | |
| 5.1.1 | 7 / 11 | |
| 5.1.0 | 7 / 11 | |
| 5.0.2 | 1 / 15 | |
| 5.0.1 | 1 / 15 | |
| 5.0.0 | 1 / 15 |
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.
v5.0.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.