@ensdomains/content-hash

A simple tool to encode/decode content hash for EIP 1577 compliant ENS Resolvers (fork of pldespaigne/content-hash)

@ensdomains/content-hash@3.1.1 was published on 2026-06-18. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.

All @ensdomains/content-hash versions · Permanent reference to 3.1.1

Package specifications

Version3.1.1
License declarationMIT
Published2026-06-18T09:33:16.531Z
Node.js requirement>=18
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size39.92 KiB
Published file count25
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies4
Repository stars14
Repository forks14

Install @ensdomains/content-hash 3.1.1

npm install @ensdomains/content-hash@3.1.1
pnpm add @ensdomains/content-hash@3.1.1
yarn add @ensdomains/content-hash@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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained9/10 — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Code-Review2/10 — Found 4/15 approved changesets -- score normalized to 2
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Packaging10/10 — packaging workflow detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness