@svar-ui/svelte-grid
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@svar-ui/lib-state | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly via bundled Svelte components, not a direct import. | ai | |
| phantom-deps | phantom-dep:@svar-ui/svelte-core | AI (phantom-deps): Same-org dep; consistent with Svelte component library pattern where deps are re-exported. | ai | |
| phantom-deps | phantom-dep:@svar-ui/grid-locales | AI (phantom-deps): Same-org dep; locale bundles are commonly declared but not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@svar-ui/grid-data-provider | AI (phantom-deps): Same-org dep; data provider pattern consistent with indirect/re-exported usage. | ai |
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.