← Home

@metaplex-foundation/umi-serializers

8
Versions
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 missing-githead AI (provenance): Benign publish-env change on trusted Metaplex package; no material diff. ai
provenance no-provenance AI (provenance): Absence of Sigstore provenance is not a risk for this established package. ai
dependencies unvetted-dep:@metaplex-foundation/umi-serializers-core AI (dependencies): Sibling package in the Metaplex UMI monorepo; same org, same version constraint, expected internal dependency. ai
dependencies unvetted-dep:@metaplex-foundation/umi-options AI (dependencies): Sibling package in the Metaplex UMI monorepo; same org, same version constraint, expected internal dependency. ai
dependencies unvetted-dep:@metaplex-foundation/umi-serializers-encodings AI (dependencies): Sibling package in the Metaplex UMI monorepo; same org, same version constraint, expected internal dependency. ai
dependencies unvetted-dep:@metaplex-foundation/umi-serializers-numbers AI (dependencies): Sibling package in the Metaplex UMI monorepo; same org, same version constraint, expected internal dependency. ai
dependencies unvetted-dep:@metaplex-foundation/umi-public-keys AI (dependencies): Sibling package in the Metaplex UMI monorepo; same org, same version constraint, expected internal dependency. ai

Versions (showing 8 of 8)

Version Deps Published
1.5.1 5 / 2
1.4.1 5 / 2
1.4.0 5 / 2
1.3.0 5 / 2
1.2.0 5 / 2
1.1.1 5 / 2
1.1.0 5 / 2
1.0.0 5 / 2

v1.2.0

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