@yuants/vendor-turboflow
TurboFlow DEX vendor integration for Yuan trading system.
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 | no-provenance | AI (provenance): Scoped internal package; provenance attestation is a best-practice recommendation, not a blocker. | ai | |
| dependencies | unvetted-dep:@yuants/utils | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| dependencies | unvetted-dep:@yuants/exchange | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| dependencies | unvetted-dep:@yuants/protocol | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| dependencies | unvetted-dep:@yuants/data-account | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| dependencies | unvetted-dep:@yuants/data-product | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| dependencies | unvetted-dep:@yuants/data-order | AI (dependencies): Internal monorepo sibling dep; consistent pattern across @yuants/* packages. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is explicitly declared in package.json dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.2.44 | 7 / 8 | |
| 1.2.43 | 7 / 8 | |
| 1.2.42 | 7 / 8 | |
| 1.2.38 | 7 / 8 | |
| 1.2.30 | 7 / 8 | |
| 1.2.27 | 7 / 6 | |
| 1.2.24 | 7 / 6 | |
| 1.2.22 | 7 / 6 | |
| 1.2.19 | 7 / 6 | |
| 1.2.11 | 7 / 6 | |
| 1.2.6 | 7 / 6 | |
| 1.2.3 | 7 / 6 | |
| 1.2.2 | 7 / 6 |
v1.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.