eth-keyring-controller 3.1.1

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

eth-keyring-controller@3.1.1 was published on 2018-04-20. Its manifest declares 10 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: Renamed to "@metamask/eth-keyring-controller"

All eth-keyring-controller versions · Permanent reference to 3.1.1 · Latest release

Package specifications

Version3.1.1
License declarationISC
Published2018-04-20T21:07:17.951Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count10
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size35.09 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies196
Repository stars226
Repository forks126

Install eth-keyring-controller 3.1.1

npm install eth-keyring-controller@3.1.1
pnpm add eth-keyring-controller@3.1.1
yarn add eth-keyring-controller@3.1.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