@uniswap/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@uniswap/v3-core | AI (phantom-deps): Same-org dependency; typical for Uniswap contract packages. | ai | |
| phantom-deps | phantom-dep:@uniswap/v3-periphery | AI (phantom-deps): Same-org dependency; typical for Uniswap contract packages. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): Config-referenced dependency; stable pattern for contract packages. | ai |
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (noahwz) than the most recent previously approved version (moodysalem) on 2021-11-23, but noahwz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.