@marianmeres/stuic
[](https://www.npmjs.com/package/@marianmeres/stuic) [](LICENSE)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@marianmeres/countries | AI (dependencies): Same-org dep from a publisher with 85 approved packages; consistent with this package's established dependency pattern. | ai | |
| phantom-deps | phantom-dep:runed | AI (phantom-deps): SvelteKit Svelte 5 library; runed is a Svelte 5 runes utility used at component level, not directly imported in analyzed entry points. | ai | |
| phantom-deps | phantom-dep:esm-env | AI (phantom-deps): esm-env is a build-time env utility common in SvelteKit packages; not directly imported in analyzed entry points. | ai | |
| phantom-deps | phantom-dep:@marianmeres/parse-boolean | AI (phantom-deps): Same-org dependency; likely used in component internals not caught by static import analysis. | ai |
Versions (showing 6 of 311)
| Version | Deps | Published |
|---|---|---|
| 2.1.17 | 8 / 20 | |
| 2.1.16 | 8 / 20 | |
| 2.1.15 | 8 / 20 | |
| 2.1.14 | 8 / 20 | |
| 2.1.13 | 8 / 20 | |
| 2.1.12 | 8 / 20 |
v2.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.