Adoption Check
Intended use: Example: lighter alternative for JWT verification
Last checked 19 Oct 2026, 05:16 UTC · method 2026-10-12.2
85% of weight had data (partial)
hokaccha/node-jwt-simple is assessed as Risky due to lack of active maintenance and weak security posture. It has seen no release and no default-branch commit in the last 365 days, with the last commit occurring 2,014 days ago. Additionally, its OpenSSF Scorecard score is 2.8 out of 10 and it lacks a security policy.
None of the 2 known vulnerabilities for jwt-simple (npm) affect the latest version (0.5.6).
Source: None of the 2 known vulnerabilities for jwt-simple (npm) affect the latest version (0.5.6).
Licensed under MIT (OSI-approved).
Source: Licensed under MIT (OSI-approved).
156,446 downloads last week on npm.
Source: 156,446 downloads last week on npm.
No release and no default-branch commit in the last 365 days.
Source: No release and no default-branch commit in the last 365 days.
OpenSSF Scorecard score is 2.8 out of 10.
Source: OpenSSF Scorecard score is 2.8 out of 10.
Last commit to the default branch was 2,014 days ago.
Source: Last commit to the default branch was 2,014 days ago.
Uncertainty: Issue responsiveness was evaluated with a sample size of only 1 issue, PR responsiveness had 0 sampled, and CI status is unknown.
Written by Gemini Flash from the metrics and reasons below; every number was checked against the data, and the verdict and score come from fixed rules, not the model.
Explained
7 concerns5 neutral3 positive
Score 41 from 85% of the weight; 1 hard gate applied.Breakdown
Weight 20
28Risky
Weight 15
100Healthy
Weight 15
5Risky
Weight 10
10Risky
from tags (no GitHub Releases)
Weight 10
—No data
Insufficient data: Only 1 recent issues or PRs to sample
Weight 10
20Risky
Partial data: contributor count only
Weight 10
60Watch
Weight 5
—No data
Insufficient data: No checks or statuses on the default branch head
Weight 5
82Healthy
Over time
History
No decision recorded yet. Status: Evaluating.