@vxrn/react-native-prebuilt
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is structural, not indicative of spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across vxrn monorepo packages; not a spam signal here. | ai | |
| phantom-deps | phantom-dep:import-meta-resolve | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vxrn/vite-native-hmr | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 19 of 519)
| Version | Deps | Published |
|---|---|---|
| 1.1.135 | 5 / 4 | |
| 1.1.134 | 5 / 4 | |
| 1.1.133 | 5 / 4 | |
| 1.1.132 | 5 / 4 | |
| 1.1.131 | 5 / 4 | |
| 1.1.130 | 5 / 4 | |
| 1.1.129 | 5 / 4 | |
| 1.1.128 | 5 / 4 | |
| 1.1.127 | 5 / 4 | |
| 1.1.126 | 5 / 4 | |
| 1.1.125 | 5 / 4 | |
| 1.1.124 | 5 / 4 | |
| 1.1.123 | 5 / 4 | |
| 1.1.122 | 5 / 4 | |
| 1.1.121 | 5 / 4 | |
| 1.1.120 | 5 / 4 | |
| 1.1.119 | 5 / 4 | |
| 1.1.118 | 5 / 4 | |
| 1.1.117 | 5 / 4 |
v1.1.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.