@metamask/eth-keyring-controller 17.0.1

A module for managing various keyrings of Ethereum accounts, encrypting them, and using them

@metamask/eth-keyring-controller@17.0.1 was published on 2024-01-22. Its manifest declares 8 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=16.0.0.

All @metamask/eth-keyring-controller versions · Permanent reference to 17.0.1 · Latest release

Package specifications

Version17.0.1
License declarationISC
Published2024-01-22T11:07:42.915Z
Node.js requirement>=16.0.0
Type declarationsBundled declarations
Runtime dependency count8
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size184.17 KiB
Published file count31
Package typeNot declared
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies64
Repository stars226
Repository forks126

Install @metamask/eth-keyring-controller 17.0.1

npm install @metamask/eth-keyring-controller@17.0.1
pnpm add @metamask/eth-keyring-controller@17.0.1
yarn add @metamask/eth-keyring-controller@17.0.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness