@veloxts/web
React Server Components integration for VeloxTS framework using Vinxi
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:vinxi | AI (dependencies): vinxi is the documented RSC build tool this package is explicitly built around; expected dependency. | ai | |
| dependencies | unvetted-dep:@vinxi/server-functions | AI (dependencies): Companion package to vinxi for server functions; consistent with package purpose. | ai | |
| phantom-deps | phantom-dep:@vinxi/server-functions | AI (phantom-deps): Config-only reference to @vinxi/server-functions is expected for a Vinxi-based RSC framework package. | ai | |
| provenance | no-provenance | AI (provenance): Common for npm packages; no other risk signals present to elevate this. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 5 / 15 | |
| 0.8.2 | 5 / 15 | |
| 0.8.0 | 5 / 15 | |
| 0.7.8 | 5 / 15 | |
| 0.7.7 | 5 / 15 | |
| 0.6.105 | 5 / 15 | |
| 0.6.103 | 5 / 16 | |
| 0.6.101 | 5 / 16 | |
| 0.6.93 | 5 / 16 | |
| 0.6.92 | 5 / 16 | |
| 0.6.87 | 5 / 16 | |
| 0.6.84 | 5 / 16 | |
| 0.6.82 | 5 / 16 | |
| 0.6.78 | 5 / 16 | |
| 0.6.77 | 5 / 16 | |
| 0.6.74 | 5 / 16 | |
| 0.6.72 | 5 / 16 | |
| 0.6.71 | 5 / 16 | |
| 0.6.70 | 5 / 16 | |
| 0.6.65 | 5 / 16 | |
| 0.6.60 | 5 / 16 | |
| 0.6.58 | 5 / 16 | |
| 0.6.56 | 5 / 16 | |
| 0.6.51 | 5 / 16 | |
| 0.6.26 | 4 / 16 | |
| 0.6.25 | 4 / 16 |
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.