jsonld-signatures 5.0.1
An implementation of the Linked Data Signatures specifications for JSON-LD in JavaScript.
jsonld-signatures@5.0.1 was published on 2020-02-28. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.
All jsonld-signatures versions · Permanent reference to 5.0.1 · Latest release
Package specifications
| Version | 5.0.1 |
|---|---|
| License declaration | BSD-3-Clause |
| Published | 2020-02-28T04:33:46.188Z |
| Node.js requirement | >=8 |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 583.65 KiB |
| Published file count | 31 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/jsonld-signatures.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 67 |
| Repository stars | 138 |
| Repository forks | 44 |
Install jsonld-signatures 5.0.1
npm install jsonld-signatures@5.0.1 pnpm add jsonld-signatures@5.0.1 yarn add jsonld-signatures@5.0.1
Runtime dependencies
- jsonld ^2.0.2
- base64url ^3.0.1
- crypto-ld ^3.7.0
- node-forge ^0.9.1
- serialize-error ^5.0.0
- security-context ^4.0.0
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.
- base64url@3.0.1 — direct
- crypto-ld@3.9.0 — direct
- jsonld@2.0.2 — direct
- node-forge@0.9.2 — direct
- security-context@4.0.0 — direct
- serialize-error@5.0.0 — direct
- base64url-universal@1.1.0 — indirect
- bs58@4.0.1 — indirect
- node-forge@0.10.0 — indirect
- semver@6.3.1 — indirect
- sodium-native@3.4.1 — indirect
- canonicalize@1.0.8 — indirect
- lru-cache@5.1.1 — indirect
- rdf-canonize@1.2.0 — indirect
- request@2.88.2 — indirect
- xmldom@0.1.19 — indirect
- type-fest@0.8.1 — indirect
- base-x@3.0.11 — indirect
- node-gyp-build@4.8.4 — indirect
- yallist@3.1.1 — indirect
- node-forge@0.10.0 — indirect
- aws-sign2@0.7.0 — indirect
- aws4@1.13.2 — indirect
- caseless@0.12.0 — indirect
- combined-stream@1.0.8 — indirect
- extend@3.0.2 — indirect
- forever-agent@0.6.1 — indirect
- form-data@2.3.3 — indirect
- har-validator@5.1.5 — indirect
- http-signature@1.2.0 — indirect
- is-typedarray@1.0.0 — indirect
- isstream@0.1.2 — indirect
- json-stringify-safe@5.0.1 — indirect
- mime-types@2.1.35 — indirect
- oauth-sign@0.9.0 — indirect
- performance-now@2.1.0 — indirect
- qs@6.5.5 — indirect
- safe-buffer@5.2.1 — indirect
- tough-cookie@2.5.0 — indirect
- tunnel-agent@0.6.0 — indirect
- uuid@3.4.0 — indirect
- delayed-stream@1.0.0 — indirect
- asynckit@0.4.0 — indirect
- ajv@6.15.0 — indirect
- har-schema@2.0.0 — indirect
- assert-plus@1.0.0 — indirect
- jsprim@1.4.2 — indirect
- sshpk@1.18.0 — indirect
- mime-db@1.52.0 — indirect
- psl@1.15.0 — indirect
- punycode@2.3.1 — indirect
- fast-deep-equal@3.1.3 — indirect
- fast-json-stable-stringify@2.1.0 — indirect
- json-schema-traverse@0.4.1 — indirect
- uri-js@4.4.1 — indirect
- extsprintf@1.3.0 — indirect
- json-schema@0.4.0 — indirect
- verror@1.10.0 — indirect
- asn1@0.2.6 — indirect
- bcrypt-pbkdf@1.0.2 — indirect
- dashdash@1.14.1 — indirect
- ecc-jsbn@0.1.2 — indirect
- getpass@0.1.7 — indirect
- jsbn@0.1.1 — indirect
- safer-buffer@2.1.2 — indirect
- tweetnacl@0.14.5 — indirect
- core-util-is@1.0.2 — indirect
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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 1/10 — Found 3/25 approved changesets -- score normalized to 1 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/jsonld-signatures/5.0.1 — retrieved 2026-10-31T16:04:11.997Z
- https://api.deps.dev/v3/projects/github.com%2Fdigitalbazaar%2Fjsonld-signatures — retrieved 2026-10-31T16:04:02.812Z
- https://api.deps.dev/v3/systems/npm/packages/jsonld-signatures/versions/5.0.1 — retrieved 2026-10-31T16:04:12.458Z
- https://api.deps.dev/v3/systems/npm/packages/jsonld-signatures/versions/5.0.1:dependencies — retrieved 2026-10-31T16:04:12.501Z