nacl-did 1.0.1

Resolve and manage DIDs using NaCL crypto suites

nacl-did@1.0.1 was published on 2020-01-20. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All nacl-did versions · Permanent reference to 1.0.1 · Latest release

Package specifications

Version1.0.1
License declarationApache-2.0
Published2020-01-20T10:51:06.548Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size135.50 KiB
Published file count25
Package typeNot declared
ES module entrylib/nacldid.modern.js
Default entrylib/nacldid.umd.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars7
Repository forks2

Install nacl-did 1.0.1

npm install nacl-did@1.0.1
pnpm add nacl-did@1.0.1
yarn add nacl-did@1.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.

Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review1/10 — Found 4/21 approved changesets -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
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