MaintainerPulse

temporal prediction of dependency maintenance risk
3,733
packages scored weekly
40%
high risk of no release in 12 months
62%
effectively single-maintainer (bus factor ≥ 0.9)
12%
of high-risk already archived or deleted on GitHub

Risk distribution across the universe

calibrated P(no release in the next 12 months), all scored packages
05001k0%-5%: 471 packages5%-10%: 230 packages10%-15%: 78 packages15%-20%: 155 packages20%-25%: 123 packages25%-30%: 118 packages30%-35%: 39 packages35%-40%: 192 packages40%-45%: 51 packages45%-50%: 127 packages50%-55%: 208 packages55%-60%: 199 packages60%-65%: 142 packages65%-70%: 108 packages70%-75%: 42 packages75%-80%: 248 packages80%-85%: 129 packages85%-90%: 221 packages90%-95%: 256 packages95%-100%: 596 packages0%50%100%

Abandonment is rising

share of packages with no release in the following 12 months, by snapshot year
0%50%100%2018202020222024

Highest risk right now (top + mid download tiers)

packageno release 12mo unresponsivecollapse
envsubst 100% 83% 100%
jinja2-strcase 100% 54% 100%
requests-auth-aws-sigv4 100% 78% 100%
pytest-extra-durations 100% 57% 100%
xlrd3 100% 54% 100%
local-crontab 100% 78% 100%
pkgutil-resolve-name 100% 75% 100%
gibberish-detector 100% 79% 100%
flask-awscognito 100% 67% 100%
asyncmock 100% 61% 100%
py2neo-history 100% 67% 100%
unix-ar 100% 57% 100%
awkward0 100% 79% 100%
confluent-avro 100% 75% 100%
llm-dialog-manager 100% 57% 100%

See the ecosystem view for the packages other projects depend on most.