@luxamm/v3-staker
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@luxamm/v3-core | AI (phantom-deps): Solidity compile-time dependency; not directly imported in JS. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@luxamm/v3-periphery | AI (phantom-deps): Solidity compile-time dependency; not directly imported in JS. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): Solidity compile-time dependency referenced in config; not directly imported in JS. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@uniswap/v3-staker | AI (dependencies): @uniswap/v3-staker is the canonical Uniswap v3 staker; this package is explicitly a re-export wrapper of it. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 3 / 31 | |
| 1.0.4 | 3 / 31 | |
| 1.0.3 | 3 / 31 | |
| 1.0.2 | 3 / 31 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.