← Home

multibase

npm Repository Homepage

JavaScript implementation of the multibase specification

25
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

vmxdaviddiasdignifiedquireachingbrainolizillahugomrdias

Keywords

IPFSmultiformatsmultibaseencodedecodeformats

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): achingbrain is a long-standing contributor (listed in package.json) and highly trusted publisher (761 approved/0 rejected). Transition from hugomrdias is legitimate. ai
maintainer-change maintainer-added AI (maintainer-change): achingbrain was already a contributor to this package before becoming a maintainer; the addition reflects a legitimate role change within the multiformats org. ai

Versions (showing 25 of 25)

Version Deps Published
4.0.6 1 / 3
4.0.5 1 / 2
4.0.4 1 / 2
4.0.3 1 / 2
4.0.2 2 / 2
4.0.1 2 / 2
3.1.2 2 / 2
3.1.1 2 / 2
3.1.0 2 / 2
3.0.1 2 / 2
3.0.0 2 / 2
2.0.0 3 / 2
1.0.1 2 / 5
1.0.0 2 / 5
0.7.0 2 / 4
0.6.1 2 / 4
0.6.0 1 / 4
0.5.0 1 / 4
0.4.0 1 / 4
0.3.4 1 / 3
0.3.3 1 / 3
0.3.2 1 / 3
0.3.1 1 / 3
0.3.0 1 / 3
0.2.0 1 / 3

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

2 findings
HIGH Publisher changed: hugomrdias → achingbrain (on 2021-08-12) provenance

This version was published by a different npm account than previous versions on 2021-08-12. 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.

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vmx → hugomrdias (on 2020-11-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-20. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hugomrdias → vmx (on 2020-09-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-18. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hugomrdias → vmx (on 2020-07-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-31. This could indicate a legitimate maintainer transition or an account compromise.