@bananapus/omnichain-deployers-v6
`@bananapus/omnichain-deployers-v6` launches Juicebox projects with cross-chain suckers and a 721 hook already wired in. It is the package you use when the default project shape should be omnichain from day one.
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:@uniswap/v4-core | AI (phantom-deps): Config-referenced dependency; stable pattern for Solidity projects. | ai | |
| phantom-deps | phantom-dep:@bananapus/core-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai | |
| phantom-deps | phantom-dep:@bananapus/ownable-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai | |
| phantom-deps | phantom-dep:@bananapus/suckers-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai | |
| phantom-deps | phantom-dep:@bananapus/721-hook-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): Config-referenced dependency; stable pattern for Solidity projects. | ai | |
| phantom-deps | phantom-dep:@bananapus/buyback-hook-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai | |
| phantom-deps | phantom-dep:@bananapus/permission-ids-v6 | AI (phantom-deps): Same-org scope; needed for compilation, not direct imports. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.0.64 | 6 / 4 | |
| 0.0.63 | 6 / 4 | |
| 0.0.62 | 6 / 4 | |
| 0.0.61 | 6 / 4 | |
| 0.0.60 | 6 / 4 | |
| 0.0.59 | 6 / 4 | |
| 0.0.58 | 6 / 4 | |
| 0.0.57 | 6 / 4 | |
| 0.0.56 | 6 / 4 | |
| 0.0.55 | 6 / 4 | |
| 0.0.54 | 6 / 4 | |
| 0.0.53 | 6 / 4 | |
| 0.0.52 | 6 / 4 | |
| 0.0.51 | 6 / 4 | |
| 0.0.50 | 6 / 4 | |
| 0.0.49 | 6 / 4 | |
| 0.0.48 | 6 / 4 | |
| 0.0.47 | 6 / 4 | |
| 0.0.46 | 6 / 4 | |
| 0.0.45 | 6 / 4 | |
| 0.0.44 | 6 / 4 | |
| 0.0.43 | 6 / 4 | |
| 0.0.42 | 6 / 4 | |
| 0.0.41 | 6 / 4 | |
| 0.0.40 | 6 / 4 | |
| 0.0.39 | 6 / 4 | |
| 0.0.38 | 6 / 4 | |
| 0.0.37 | 6 / 4 | |
| 0.0.35 | 6 / 4 | |
| 0.0.34 | 6 / 4 | |
| 0.0.31 | 8 / 2 | |
| 0.0.30 | 8 / 2 | |
| 0.0.29 | 8 / 2 | |
| 0.0.28 | 8 / 2 | |
| 0.0.27 | 8 / 2 | |
| 0.0.26 | 8 / 2 | |
| 0.0.25 | 8 / 2 | |
| 0.0.24 | 8 / 2 | |
| 0.0.23 | 8 / 2 | |
| 0.0.22 | 8 / 1 | |
| 0.0.21 | 8 / 1 | |
| 0.0.20 | 9 / 1 | |
| 0.0.19 | 9 / 1 | |
| 0.0.18 | 9 / 1 | |
| 0.0.17 | 9 / 1 | |
| 0.0.16 | 9 / 1 | |
| 0.0.15 | 9 / 1 | |
| 0.0.14 | 8 / 1 | |
| 0.0.13 | 8 / 1 | |
| 0.0.12 | 8 / 1 | |
| 0.0.11 | 8 / 1 |
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.44
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.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
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.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.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.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.