@tummycrypt/tinyland-composables
Svelte 5 rune-based composables for reactive state management, lifecycle utilities, theming, and Web Worker synchronization
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:@tummycrypt/sveltekit-shims | AI (dependencies): Same org scope (@tummycrypt); sibling package in the same monorepo, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tummycrypt/sveltekit-shims | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires because it may be used indirectly via re-exports rather than direct import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 0 / 8 | |
| 0.2.3 | 0 / 8 | |
| 0.2.2 | 0 / 7 | |
| 0.2.1 | 1 / 8 | |
| 0.2.0 | 1 / 7 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.