← Home

@metamask/auth-network-utils

common utilities to access and format responses from auth network

3
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

danfinlaykumavismcmirerekmarksmetamaskbotgudahttnicholasellulsethkfmannaugtur

Keywords

MetaMaskEthereum

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:elliptic AI (dependencies): elliptic is a standard crypto library; expected dependency for MetaMask auth/crypto utilities. ai
dependencies unvetted-dep:@toruslabs/bs58 AI (dependencies): Torus Labs bs58 is a known utility used in Web3/MetaMask ecosystem; appropriate for this package. ai
provenance no-provenance AI (provenance): MetaMask org package published via metamaskbot; low risk without provenance given publisher track record. ai
phantom-deps phantom-dep:loglevel AI (phantom-deps): loglevel is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@toruslabs/bs58 AI (phantom-deps): Declared runtime dep; may be used indirectly via re-exports or config; stable false positive. ai
phantom-deps phantom-dep:@toruslabs/constants AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 3 of 3)

Version Deps Published
0.4.0 9 / 11
0.2.0 9 / 10
0.1.0 9 / 10

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

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

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