Skip to report

Independent analytics for a public GitHub repository

1andrevich/Re-filter-lists

Re:filter is (an attempt to create) an actual list of blocked domains and IPs in RU + popular and blocked for RU users — view on GitHub · github.com/1andrevich/Re-filter-lists

Language

Python

License

MIT

open source

Created

Sep 2024

Stars

1,318

Forks

59

Issues

29 open

Updated 21 Sept 2026, 18:22 UTC

40 /100
SLOWING

tracker score 40/100 methodology →

Computed from release cadence, responsiveness, backlog trend and contributor depth.

Last release

48 days ago

01082026

Cadence

every 18.6d

48d gap

PR merge median

15.4d

Issue response median

78.3h

Commits / 7d

0

Attention vs delivery — is popularity translating into shipping?

The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.

attention — commits / month delivery — merged PRs / month stable release

Reading: delivery held at ~8 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.

Responsiveness — vs cohort percentiles

How fast maintainers answer, review and merge — ranked against repos of similar size and age.

Issue first non-author response

median 78.3hcohort: n/a

PR first review

median 5.8dcohort: n/a

PR merge time

median 15.4dcohort: n/a

Bots excluded Sample: 6 merged PRs (90d) / 37 recent issues. Percentile position measured from the left — shorter is faster.

First-contributor funnel — what happens to a newcomer’s PR?

0

first-time PRs (12 mo)

—

got a response

n=27 scanned

—

were merged

0 newcomer candidates

—

returned ≤90d

verified via author history

Verdict: 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.

Contributor concentration (12 mo)

top 1 — 59.7% of accepted changes · last commit Jun 28

top 3 — 97.8% of accepted changes

long tail — 3 further authors

Verdict: high key-person risk. 6 human commit authors in 12 months; top author (1andrevich) holds 59.7%, top 3 hold 97.8%, 3 authors above 1% each.

Open-issue backlog

Open issues and pull requests right now. Trend history builds from daily tracking.

open issues & PRs — right now

29

open issues

18

open pull requests

Tracking daily since 2 Sept 2026 — 4 snapshots so far. Score moved 45 → 40 over the past 19d.

47 open

29 issues + 18 PRs · backlog up 15% over 19d

Fork network & successors

59 forks · 0 with independent momentum

xyzmean/Re-filter-lists — 2★ · last push 1d ago

alive

1andrevich/Re-filter-lists 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.

What changed — last 90d

2 stable releases in 90d (median gap 18.6d)

Issue response sits at a 78.3h median — down from 138.1h 19d ago

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 56d (cadence 18.6d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is Re-filter-lists still maintained?

Partially — activity is slowing (score 40/100). Last stable release 01082026 48 days ago, 0 commits in the last full week, median PR merge 15.4d. Evidence collected Mon Sep 21 2026.

What license does Re-filter-lists use?

MIT — as reported by GitHub.

When was the last Re-filter-lists release?

01082026, 48 days ago. Median gap between stable releases is 18.6 days; 2 stable releases shipped in the last 90 days — the current 48d gap is well above that median.

Is Re-filter-lists safe to adopt for a new project in 2026?

On the evidence: caution. 6 human authors in 12 months, no fork-succession pressure. Not published to npm — GitHub activity only.

Share & embed — every share is a branded mini-report

Link preview (auto-generated OG card)

tracker.git.tools

1andrevich/Re-filter-lists

SLOWING · 40/100

ships every 18.6d · PR merge 15.4d · ★ 1,318

1andrevich/Re-filter-lists — maintenance verdict & repo intelligence · tracker.git.tools

README badge (live SVG — every embed is a backlink)

maintenance slowing · 40
[![maintenance](https://tracker.git.tools/badge/1andrevich/Re-filter-lists)](https://tracker.git.tools/1andrevich/Re-filter-lists)

Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.

Methodology

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.