did-jwt 0.2.0-alpha4

Library for Signing and Verifying JWTs compatible uPort and DID standards

did-jwt@0.2.0-alpha4 was published on 2019-02-23. Its manifest declares 9 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.

All did-jwt versions · Permanent reference to 0.2.0-alpha4 · Latest release

Package specifications

Version0.2.0-alpha4
License declarationApache-2.0
Published2019-02-23T16:51:13.253Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count9
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size146.94 KiB
Published file count24
Package typeNot declared
ES module entrylib/index.esm.js
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies18
Repository stars373
Repository forks78

Install did-jwt 0.2.0-alpha4

npm install did-jwt@0.2.0-alpha4
pnpm add did-jwt@0.2.0-alpha4
yarn add did-jwt@0.2.0-alpha4

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
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
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Security-Policy0/10 — security policy file not detected

Evidence and freshness