@viamrobotics/prime-core
`@viamrobotics/prime-core` is a collection of core Svelte components.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is a documented CI/CD migration for viamrobotics org; stable going forward. | ai | |
| phantom-deps | phantom-dep:@zag-js/svelte | AI (phantom-deps): Referenced in config files per analyzer note; not a true phantom dep for this Svelte component library. | ai | |
| phantom-deps | phantom-dep:@zag-js/collapsible | AI (phantom-deps): Referenced in config files per analyzer note; not a true phantom dep for this Svelte component library. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.1.21 | 19 / 35 | |
| 0.1.20 | 19 / 35 | |
| 0.1.19 | 8 / 35 | |
| 0.1.18 | 8 / 35 | |
| 0.1.17 | 8 / 35 | |
| 0.1.16 | 8 / 35 | |
| 0.1.15 | 8 / 35 | |
| 0.1.14 | 8 / 35 | |
| 0.1.13 | 8 / 35 | |
| 0.1.12 | 8 / 35 | |
| 0.1.11 | 8 / 35 | |
| 0.1.10 | 8 / 35 | |
| 0.1.9 | 8 / 35 | |
| 0.1.8 | 8 / 35 | |
| 0.1.7 | 8 / 35 | |
| 0.1.6 | 5 / 31 | |
| 0.1.5 | 7 / 32 |
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.