@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@viamrobotics/tailwind-config | AI (dependencies): Same-org first-party dependency, not third-party supply chain risk. | ai | |
| phantom-deps | phantom-dep:@viamrobotics/tailwind-config | AI (phantom-deps): Same-org config package likely used via build tooling, not direct import. | ai | |
| 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 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.1.23 | 20 / 44 | |
| 0.1.22 | 19 / 35 | |
| 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 | |
| 0.1.4 | 7 / 32 | |
| 0.1.3 | 7 / 32 | |
| 0.1.2 | 7 / 32 | |
| 0.1.1 | 7 / 29 | |
| 0.1.0 | 7 / 29 | |
| 0.0.180 | 7 / 37 | |
| 0.0.179 | 7 / 37 | |
| 0.0.178 | 7 / 37 | |
| 0.0.177 | 7 / 37 | |
| 0.0.176 | 7 / 37 | |
| 0.0.175 | 7 / 37 | |
| 0.0.174 | 7 / 37 | |
| 0.0.173 | 7 / 37 | |
| 0.0.172 | 7 / 37 | |
| 0.0.171 | 7 / 37 | |
| 0.0.170 | 7 / 37 | |
| 0.0.169 | 7 / 37 | |
| 0.0.168 | 7 / 37 | |
| 0.0.167 | 7 / 37 | |
| 0.0.166 | 7 / 37 | |
| 0.0.165 | 7 / 37 | |
| 0.0.164 | 7 / 37 | |
| 0.0.163 | 7 / 37 | |
| 0.0.162 | 7 / 37 | |
| 0.0.161 | 7 / 37 | |
| 0.0.160 | 7 / 37 | |
| 0.0.159 | 7 / 37 | |
| 0.0.158 | 7 / 37 | |
| 0.0.157 | 7 / 37 | |
| 0.0.156 | 7 / 37 | |
| 0.0.155 | 7 / 37 | |
| 0.0.154 | 7 / 37 | |
| 0.0.153 | 7 / 37 | |
| 0.0.152 | 7 / 37 | |
| 0.0.151 | 7 / 37 | |
| 0.0.150 | 7 / 37 | |
| 0.0.149 | 7 / 37 | |
| 0.0.148 | 7 / 37 | |
| 0.0.147 | 7 / 37 | |
| 0.0.146 | 7 / 37 | |
| 0.0.145 | 7 / 37 | |
| 0.0.144 | 7 / 37 | |
| 0.0.143 | 7 / 37 | |
| 0.0.142 | 7 / 37 | |
| 0.0.141 | 7 / 37 | |
| 0.0.140 | 7 / 37 | |
| 0.0.139 | 7 / 37 | |
| 0.0.138 | 7 / 37 | |
| 0.0.137 | 7 / 37 | |
| 0.0.136 | 7 / 37 | |
| 0.0.135 | 7 / 37 | |
| 0.0.134 | 7 / 37 | |
| 0.0.133 | 7 / 37 | |
| 0.0.132 | 7 / 37 | |
| 0.0.131 | 7 / 37 | |
| 0.0.130 | 7 / 37 | |
| 0.0.129 | 7 / 37 | |
| 0.0.128 | 7 / 37 | |
| 0.0.127 | 7 / 37 | |
| 0.0.126 | 7 / 37 | |
| 0.0.125 | 7 / 37 | |
| 0.0.124 | 7 / 37 | |
| 0.0.123 | 7 / 37 | |
| 0.0.122 | 7 / 37 | |
| 0.0.121 | 7 / 37 | |
| 0.0.120 | 7 / 37 | |
| 0.0.119 | 7 / 37 | |
| 0.0.118 | 7 / 37 | |
| 0.0.117 | 7 / 37 | |
| 0.0.116 | 7 / 37 |
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (micheal.parks) than the most recent previously approved version (viambot) on 2025-03-04, but micheal.parks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (micheal.parks) than the most recent previously approved version (viambot) on 2025-03-03, but micheal.parks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.