Adoption Check
Intended use: Example: customer login with passkeys and two-factor auth
Last checked 19 Oct 2026, 05:15 UTC · method 2026-10-12.2
80% of weight had data (partial)
better-auth/better-auth has a verdict of Healthy based on strong adoption, rapid release cadence, and the fact that none of the 22 known vulnerabilities for better-auth (npm) affect the latest version (1.7.11). However, there are potential concerns regarding 31 GitHub security advisories published in the last 365 days and maintainers responding to only 23 percent of sampled items.
None of the 22 known vulnerabilities for better-auth (npm) affect the latest version (1.7.11).
Source: None of the 22 known vulnerabilities for better-auth (npm) affect the latest version (1.7.11).
171 releases in the last 365 days.
Source: 171 releases in the last 365 days.
7,564,727 downloads last week on npm.
Source: 7,564,727 downloads last week on npm.
31 GitHub security advisories published in the last 365 days.
Source: 31 GitHub security advisories published in the last 365 days.
Maintainers responded to 23 percent of sampled items.
Source: Maintainers responded to 23 percent of sampled items.
Uncertainty: Responsiveness metrics were derived from a sample of 12 issues and 50 pull requests from the last 90 days, and OpenSSF Scorecard data was missing.
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
2 concerns5 neutral11 positive
Score 87 from 80% of the weight; no hard gates applied.Breakdown
Weight 20
—No data
Insufficient data: No OpenSSF Scorecard data for this repository
Weight 15
60Watch
Weight 15
100Healthy
Weight 10
100Healthy
Weight 10
54Watch
sampled (62 items)
Weight 10
100Healthy
Weight 10
100Healthy
Weight 5
100Healthy
Weight 5
100Healthy
Over time
History
No decision recorded yet. Status: Evaluating.