← Home

@metaplex-foundation/umi-eddsa-web3js

An Eddsa implementation relying on Solana's web3.js

8
Versions
MIT
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

danenbm1nhanphanbrandontulsisvc01-metaplexdanenbmblockiosaurus

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition within Metaplex org; new publisher has clean track record. ai
provenance missing-githead AI (provenance): Publish-env metadata change; no code change, trusted maintainer. ai
dependencies unvetted-dep:@soceanfi/solana-cli-config AI (dependencies): Legitimate Solana tooling dep, stable across Metaplex umi packages. ai
phantom-deps phantom-dep:yaml AI (phantom-deps): yaml is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 8 of 8)

Version Deps Published
1.5.1 3 / 4
1.4.1 3 / 4
1.4.0 3 / 4
1.3.0 3 / 4
1.1.1 3 / 4
1.1.0 3 / 4
1.0.1 3 / 4
1.0.0 3 / 4

v1.1.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blockiosaurus.

LOW No provenance attestation provenance

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

v1.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.

v1.0.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.

v1.0.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.