← Home

@marinade.finance/validator-bonds-cli-core

npm Repository

Common CLI Core of the validator bonds contract

25
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

lj1024-marinade__chaldahamster

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Trusted publisher with strong prior track record; no malicious diff observed. ai
bogus-package bogus-package AI (bogus-package): Legitimate internal CLI package with sparse README, not spam. ai

Versions (showing 25 of 25)

Version Deps Published
2.5.0 1 / 24
2.4.8 0 / 24
2.4.7 0 / 24
2.4.6 0 / 24
2.4.5 0 / 24
2.4.4 0 / 24
2.4.3 0 / 24
2.4.2 0 / 24
2.4.1 0 / 24
2.4.0 0 / 20
2.3.2 0 / 20
2.3.1 0 / 20
2.3.0 0 / 20
2.2.3 0 / 17
2.2.2 0 / 17
2.2.1 0 / 17
2.2.0 0 / 17
2.1.10 0 / 17
2.1.9 0 / 17
2.1.8 0 / 17
2.1.7 0 / 17
2.1.3 0 / 17
2.1.2 0 / 17
2.1.1 0 / 17
2.1.0 0 / 17

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.3

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (marinade.finance) were replaced by new maintainers (lj1024-marinade, xndru, __chalda, hamster). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: marinade.finance → __chalda (on 2025-02-19) provenance

This version was published by a different npm account than previous versions on 2025-02-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.