Independent analytics for a public GitHub repository
Bittorrent DHT research tools and libs — view on GitHub · github.com/0x0d/dhtfck
Language
Python
License
MIT
open source
Created
Apr 2013
Stars
374
Forks
143
Issues
0 open
Updated 21 Sept 2026, 18:30 UTC
tracker score 10/100 methodology →
Computed from release cadence, responsiveness, backlog trend and contributor depth.
Last release
never
—
Cadence
no stable cadence
n/aPR merge median
n/a
Issue response median
6.0d
Commits / 7d
0
The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.
Reading: delivery held at ~0 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.
How fast maintainers answer, review and merge — ranked against repos of similar size and age.
Issue first non-author response
median 6.0dcohort: n/aPR first review
median 7.8hcohort: n/aPR merge time
sample too smallcohort: n/aBots excluded Sample: 0 merged PRs (90d) / 1 recent issues. Percentile position measured from the left — shorter is faster.
0
first-time PRs (12 mo)
—
got a response
n=0 scanned
—
were merged
0 newcomer candidates
—
returned ≤90d
verified via author historyVerdict: not enough first-time PRs in the sampled window (2026-03-25..2026-06-23) to call this either way — most contributions here come from people already close to the project.
stats unavailable of accepted changes · —
— of accepted changes
GitHub could not compute contributor stats for this repo
Verdict: key-person risk unknown. GitHub never computed contributor statistics for this repository (common on very large commit networks), so concentration cannot be measured.
Open issues and pull requests right now. Trend history builds from daily tracking.
open issues & PRs — right now
0
open issues
2
open pull requests
First snapshot taken today — trend lines fill in as daily snapshots accumulate.
2 open
0 issues + 2 PRs · trend builds as daily snapshots accumulate
143 forks · 0 with independent momentum
arekyao/dht-crawler — 12★ · last push 4690d ago
0x0d/dhtfck is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.
If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.
0 stable releases in 90d (no stable cadence)
Issue response sits at a 144.5h median — trend builds as daily snapshots accumulate
License unchanged · not archived · no rename/transfer
Fewer than 2 releases in 12mo — no gap to measure
These answers regenerate on every snapshot — they never rot.
No clear signs of active maintenance (score 10/100). No stable releases on record, 0 commits in the last full week, PR merge time not measurable (too few merged PRs in the 90d sample). Evidence collected Mon Sep 21 2026.
See repository — as reported by GitHub.
—
On the evidence: no. 0 human authors in 12 months, no fork-succession pressure. Not published to npm — GitHub activity only.
Link preview (auto-generated OG card)
tracker.git.tools
0x0d/dhtfck
DORMANT · 10/100
ships no stable cadence · PR merge n/a · ★ 374
0x0d/dhtfck — maintenance verdict & repo intelligence · tracker.git.tools
README badge (live SVG — every embed is a backlink)
[](https://tracker.git.tools/0x0d/dhtfck)
Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.
Get an email the week this repo’s verdict changes — release droughts, response-time decay, key-person exits. Free for 3 repos. Your whole package.json monitored, on paid.
This report for your private org repos →Verdict-change alerts, release droughts, response-time decay. Free for 3 repos.
Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.