jwa 2.0.1
JWA implementation (supports all JWS algorithms)
jwa@2.0.1 was published on 2025-05-07. Its manifest declares 3 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 jwa versions · Permanent reference to 2.0.1 · Latest release
Package specifications
| Version | 2.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2025-05-07T11:42:50.147Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 13.72 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 103 |
| Repository forks | 44 |
Install jwa 2.0.1
npm install jwa@2.0.1 pnpm add jwa@2.0.1 yarn add jwa@2.0.1
Runtime dependencies
- safe-buffer ^5.0.1
- ecdsa-sig-formatter 1.0.11
- buffer-equal-constant-time ^1.0.1
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.
- buffer-equal-constant-time@1.0.1 — direct
- ecdsa-sig-formatter@1.0.11 — direct
- safe-buffer@5.2.1 — direct
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.
| Maintained | 0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 3/10 — Found 8/23 approved changesets -- score normalized to 3 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 4/10 — dependency not pinned by hash detected -- score normalized to 4 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Packaging | 10/10 — packaging workflow detected |
| Security-Policy | 10/10 — security policy file detected |
| Branch-Protection | 1/10 — branch protection is not maximal on development and all release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/jwa/2.0.1 — retrieved 2026-10-29T09:28:17.806Z
- https://api.deps.dev/v3/systems/npm/packages/jwa/versions/2.0.1 — retrieved 2026-10-29T09:28:18.291Z
- https://api.deps.dev/v3/systems/npm/packages/jwa/versions/2.0.1:dependencies — retrieved 2026-10-29T09:28:18.345Z
- https://api.deps.dev/v3/projects/github.com%2Fbrianloveswords%2Fnode-jwa — retrieved 2026-10-29T09:28:18.939Z