@bananapus/721-hook-v6
`@bananapus/721-hook-v6` is the tiered NFT issuance layer for Juicebox V6. It lets a project mint ERC-721s on payment, attach tier-specific pricing and supply rules, mint reserves, and integrate custom token URI resolvers.
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:solady | AI (phantom-deps): Solidity/Foundry package; solady is a Solidity library referenced via remappings config, not a JS import. This pattern is standard for Foundry projects. | ai | |
| phantom-deps | phantom-dep:@prb/math | AI (phantom-deps): Solidity/Foundry package; @prb/math is a Solidity library referenced via remappings config, not a JS import. Standard Foundry pattern. | ai | |
| phantom-deps | phantom-dep:@bananapus/core-v6 | AI (phantom-deps): Sibling @bananapus org Solidity package; referenced via remappings in Foundry config, not a JS import. Standard pattern. | ai | |
| phantom-deps | phantom-dep:@bananapus/ownable-v6 | AI (phantom-deps): Sibling @bananapus org Solidity package; referenced via remappings in Foundry config, not a JS import. Standard pattern. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): OpenZeppelin Solidity contracts referenced via remappings config in Foundry project, not a JS import. Standard pattern. | ai | |
| phantom-deps | phantom-dep:@bananapus/permission-ids-v6 | AI (phantom-deps): Sibling @bananapus org Solidity package; referenced via remappings in Foundry config, not a JS import. Standard pattern. | ai | |
| phantom-deps | phantom-dep:@bananapus/address-registry-v6 | AI (phantom-deps): Sibling @bananapus org Solidity package; referenced via remappings in Foundry config, not a JS import. Standard pattern. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.0.75 | 7 / 1 | |
| 0.0.74 | 7 / 1 | |
| 0.0.73 | 7 / 1 | |
| 0.0.72 | 7 / 1 | |
| 0.0.70 | 7 / 1 | |
| 0.0.69 | 7 / 1 | |
| 0.0.68 | 7 / 1 | |
| 0.0.67 | 7 / 1 | |
| 0.0.65 | 7 / 1 | |
| 0.0.64 | 7 / 1 | |
| 0.0.63 | 7 / 1 | |
| 0.0.62 | 7 / 1 | |
| 0.0.61 | 7 / 1 | |
| 0.0.60 | 7 / 1 | |
| 0.0.59 | 7 / 1 | |
| 0.0.58 | 7 / 1 | |
| 0.0.57 | 7 / 1 | |
| 0.0.56 | 7 / 1 | |
| 0.0.55 | 7 / 1 | |
| 0.0.54 | 7 / 1 | |
| 0.0.53 | 7 / 1 | |
| 0.0.52 | 7 / 1 | |
| 0.0.51 | 7 / 1 | |
| 0.0.50 | 7 / 1 | |
| 0.0.49 | 7 / 1 | |
| 0.0.47 | 7 / 1 | |
| 0.0.46 | 7 / 1 | |
| 0.0.45 | 7 / 1 | |
| 0.0.43 | 7 / 1 | |
| 0.0.42 | 7 / 1 | |
| 0.0.41 | 7 / 1 | |
| 0.0.40 | 7 / 1 | |
| 0.0.39 | 7 / 1 | |
| 0.0.38 | 7 / 1 | |
| 0.0.37 | 7 / 1 | |
| 0.0.36 | 7 / 1 | |
| 0.0.35 | 7 / 1 | |
| 0.0.34 | 7 / 1 | |
| 0.0.33 | 7 / 1 | |
| 0.0.32 | 7 / 1 | |
| 0.0.31 | 7 / 1 | |
| 0.0.30 | 7 / 1 | |
| 0.0.29 | 7 / 1 | |
| 0.0.28 | 7 / 1 | |
| 0.0.27 | 7 / 1 | |
| 0.0.26 | 7 / 1 | |
| 0.0.25 | 7 / 1 | |
| 0.0.24 | 7 / 1 | |
| 0.0.23 | 7 / 1 | |
| 0.0.22 | 7 / 1 | |
| 0.0.21 | 7 / 1 | |
| 0.0.20 | 7 / 1 | |
| 0.0.19 | 7 / 1 | |
| 0.0.18 | 7 / 1 | |
| 0.0.17 | 7 / 1 | |
| 0.0.16 | 7 / 1 | |
| 0.0.15 | 7 / 1 | |
| 0.0.14 | 7 / 1 | |
| 0.0.13 | 7 / 1 | |
| 0.0.12 | 7 / 1 | |
| 0.0.11 | 7 / 1 | |
| 0.0.10 | 7 / 1 | |
| 0.0.9 | 7 / 1 | |
| 0.0.8 | 7 / 1 | |
| 0.0.7 | 7 / 1 | |
| 0.0.6 | 7 / 1 | |
| 0.0.5 | 7 / 1 | |
| 0.0.4 | 7 / 1 | |
| 0.0.3 | 7 / 1 | |
| 0.0.2 | 7 / 1 | |
| 0.0.1 | 7 / 1 |
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.42
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.32
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. 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.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. 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. Consider requesting the maintainer enable provenance via CI/CD.
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.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.