@marinade.finance/marinade-ts-sdk
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): bs58 is a declared runtime dep used transitively; phantom-dep false positive stable for this package. | ai | |
| dependencies | unvetted-dep:@marinade.finance/native-staking-sdk | AI (dependencies): First-party sibling package from the same marinade-finance org; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 7 / 24 | |
| 5.0.18 | 6 / 25 | |
| 5.0.17 | 7 / 25 | |
| 5.0.16 | 7 / 25 |
v6.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hamster) than the most recent previously approved version (__chalda) on 2026-06-25, but hamster 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.