@bananapus/univ4-router-v6
`@bananapus/univ4-router-v6` provides the Uniswap V4 hook and oracle surface used to compare market execution with Juicebox-native execution. It is a routing primitive for projects that want protocol-aware swaps instead of blind pool usage.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:solmate | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. This is the standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@prb/math | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@uniswap/v3-core | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@uniswap/v4-core | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@bananapus/core-v6 | AI (phantom-deps): Same-org Solidity dependency declared for Foundry remappings. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@uniswap/v3-periphery | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@uniswap/v4-periphery | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/uniswap-hooks | AI (phantom-deps): Foundry/Solidity package; deps declared for remappings in foundry.toml, not JS imports. Standard pattern for Solidity packages on npm. | ai | |
| phantom-deps | phantom-dep:@bananapus/permission-ids-v6 | AI (phantom-deps): Same-org Solidity dependency declared for Foundry remappings. Standard pattern for Solidity packages on npm. | ai | |
| npm-metadata | url-dep:@uniswap/v3-core | AI (npm-metadata): GitHub URL dep pointing to Uniswap/v3-core#0.8 is the standard way to get the Solidity 0.8.x-compatible fork; well-known pattern in DeFi Solidity packages. | ai | |
| npm-metadata | url-dep:@uniswap/v3-periphery | AI (npm-metadata): GitHub URL dep pointing to Uniswap/v3-periphery#0.8 is the standard way to get the Solidity 0.8.x-compatible fork; well-known pattern in DeFi Solidity packages. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.0.59 | 5 / 3 | |
| 0.0.58 | 5 / 3 | |
| 0.0.57 | 5 / 3 | |
| 0.0.56 | 5 / 3 | |
| 0.0.55 | 5 / 3 | |
| 0.0.54 | 7 / 2 | |
| 0.0.53 | 7 / 2 | |
| 0.0.52 | 7 / 2 | |
| 0.0.51 | 7 / 2 | |
| 0.0.50 | 7 / 2 | |
| 0.0.49 | 7 / 2 | |
| 0.0.48 | 7 / 2 | |
| 0.0.47 | 7 / 2 | |
| 0.0.46 | 7 / 2 | |
| 0.0.45 | 7 / 2 | |
| 0.0.43 | 7 / 2 | |
| 0.0.40 | 7 / 2 | |
| 0.0.39 | 7 / 2 | |
| 0.0.38 | 7 / 2 | |
| 0.0.37 | 7 / 2 | |
| 0.0.36 | 7 / 2 | |
| 0.0.35 | 7 / 2 | |
| 0.0.34 | 7 / 2 | |
| 0.0.33 | 7 / 2 | |
| 0.0.31 | 7 / 2 | |
| 0.0.30 | 7 / 2 | |
| 0.0.28 | 7 / 2 | |
| 0.0.26 | 7 / 2 | |
| 0.0.25 | 7 / 2 | |
| 0.0.24 | 7 / 2 | |
| 0.0.23 | 7 / 1 | |
| 0.0.22 | 7 / 1 | |
| 0.0.21 | 10 / 1 | |
| 0.0.20 | 10 / 1 | |
| 0.0.19 | 10 / 1 | |
| 0.0.18 | 10 / 1 | |
| 0.0.17 | 10 / 1 | |
| 0.0.16 | 10 / 1 | |
| 0.0.15 | 10 / 1 | |
| 0.0.14 | 10 / 1 | |
| 0.0.13 | 10 / 1 | |
| 0.0.12 | 10 / 1 | |
| 0.0.11 | 9 / 1 | |
| 0.0.10 | 9 / 1 | |
| 0.0.9 | 9 / 1 | |
| 0.0.8 | 9 / 1 | |
| 0.0.7 | 9 / 0 | |
| 0.0.6 | 9 / 0 | |
| 0.0.5 | 9 / 0 | |
| 0.0.4 | 9 / 0 | |
| 0.0.3 | 9 / 0 |
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.