@marinade.finance/web3js-common
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
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.7.0 | 1 / 8 | |
| 3.6.1 | 1 / 8 | |
| 3.6.0 | 1 / 8 | |
| 3.5.1 | 0 / 9 | |
| 3.5.0 | 0 / 9 | |
| 3.4.0 | 0 / 9 | |
| 3.3.0 | 0 / 9 | |
| 3.2.0 | 0 / 9 | |
| 3.1.1 | 0 / 9 | |
| 3.1.0 | 0 / 9 | |
| 3.0.4 | 0 / 9 | |
| 3.0.3 | 0 / 9 | |
| 3.0.2 | 0 / 9 | |
| 3.0.1 | 0 / 6 | |
| 3.0.0 | 0 / 6 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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 (__chalda) than the most recent previously approved version (hamster) on 2025-03-28, but __chalda 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.
v3.1.0
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 (hamster) than the most recent previously approved version (__chalda) on 2025-03-24, 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.
v3.0.4
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 (__chalda) than the most recent previously approved version (hamster) on 2025-03-24, but __chalda 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.
v3.0.3
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 (hamster) than the most recent previously approved version (__chalda) on 2025-03-20, 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.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.