@vxrn/vite-native-swc
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No behavioral change vs prior approved version; likely CI/build environment quirk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package with synced version bumps across siblings; no malicious diff. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-regenerator | AI (phantom-deps): Babel plugin used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:metro-react-native-babel-preset | AI (phantom-deps): Babel preset loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-private-methods | AI (phantom-deps): Babel plugin used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-destructuring | AI (phantom-deps): Babel plugin used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx | AI (phantom-deps): Babel plugin used via config, not direct import. | ai |
Versions (showing 56 of 256)
| Version | Deps | Published |
|---|---|---|
| 1.1.189 | 2 / 3 | |
| 1.1.188 | 2 / 3 | |
| 1.1.187 | 2 / 3 | |
| 1.1.186 | 2 / 3 | |
| 1.1.185 | 2 / 3 | |
| 1.1.184 | 2 / 3 | |
| 1.1.183 | 2 / 3 | |
| 1.1.182 | 2 / 3 | |
| 1.1.181 | 2 / 3 | |
| 1.1.180 | 2 / 3 | |
| 1.1.179 | 2 / 3 | |
| 1.1.178 | 2 / 3 | |
| 1.1.177 | 2 / 3 | |
| 1.1.176 | 2 / 3 | |
| 1.1.175 | 2 / 3 | |
| 1.1.174 | 2 / 3 | |
| 1.1.173 | 2 / 3 | |
| 1.1.172 | 2 / 3 | |
| 1.1.171 | 2 / 3 | |
| 1.1.170 | 2 / 3 | |
| 1.1.169 | 2 / 3 | |
| 1.1.168 | 2 / 3 | |
| 1.1.167 | 2 / 3 | |
| 1.1.166 | 2 / 3 | |
| 1.1.165 | 2 / 3 | |
| 1.1.164 | 2 / 3 | |
| 1.1.163 | 2 / 3 | |
| 1.1.162 | 2 / 3 | |
| 1.1.161 | 2 / 3 | |
| 1.1.160 | 2 / 3 | |
| 1.1.159 | 2 / 3 | |
| 1.1.158 | 2 / 3 | |
| 1.1.157 | 2 / 3 | |
| 1.1.156 | 2 / 3 | |
| 1.1.155 | 2 / 3 | |
| 1.1.154 | 2 / 3 | |
| 1.1.153 | 2 / 3 | |
| 1.1.152 | 2 / 3 | |
| 1.1.151 | 2 / 3 | |
| 1.1.150 | 2 / 3 | |
| 1.1.149 | 2 / 3 | |
| 1.1.148 | 2 / 3 | |
| 1.1.147 | 2 / 3 | |
| 1.1.146 | 2 / 3 | |
| 1.1.145 | 2 / 3 | |
| 1.1.144 | 2 / 3 | |
| 1.1.143 | 2 / 3 | |
| 1.1.142 | 2 / 3 | |
| 1.1.141 | 2 / 3 | |
| 1.1.140 | 2 / 3 | |
| 1.1.139 | 2 / 3 | |
| 1.1.138 | 2 / 3 | |
| 1.1.137 | 2 / 3 | |
| 1.1.136 | 2 / 3 | |
| 1.1.135 | 2 / 3 | |
| 1.1.118 | 2 / 3 |
v1.1.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.