logger
R's logging package handed to new maintainers and rebuilt from the inside out
Comparison · Infra & APIs
discretetests vs Fail2Ban
A side-by-side editorial comparison of discretetests and Fail2Ban — release velocity, themes, recent moves, and the top alternatives to consider.
discretetests vs Fail2Ban: at a glance
What is discretetests?
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
What is Fail2Ban?
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
Fail2Ban watches log files for authentication failures and bans the offending addresses through the local firewall. It remains a default component of Linux server hardening, and its release cadence has never matched that prominence — six releases in the eight years before this one. The 1.1.1 final has now landed, closing a beta that had sat unfinished since June 2025, and it installs a systemd-managed socket rather than relying solely on the daemon's own startup.
discretetests vs Fail2Ban: editorial side-by-side
discretetests
0.0INFRA · APIS
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
◆ Current state
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
◆ Where it's heading
Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.
◆ Prediction
The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.
Fail2Ban
2.5INFRA · APIS
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
◆ Current state
Fail2Ban watches log files for authentication failures and bans the offending addresses through the local firewall. It remains a default component of Linux server hardening, and its release cadence has never matched that prominence — six releases in the eight years before this one. The 1.1.1 final has now landed, closing a beta that had sat unfinished since June 2025, and it installs a systemd-managed socket rather than relying solely on the daemon's own startup.
◆ Where it's heading
The pattern is long silences broken by releases that mostly absorb external change — Python 3.12 and 3.13 compatibility in 1.1.0, a Dovecot filter regression in 1.0.2 — with the substance deferred to a ChangeLog the feed does not carry. What is different this time is the contributor list, which runs to a dozen first-time contributors, suggesting the delay was throughput rather than abandonment. The release also had to be re-cut: the first Debian package shipped with wrong paths from a missing systemd-dev build dependency and was pulled and replaced.
◆ Prediction
Given the beta-to-final gap just closed and the volume of first-time contributors merged into it, the useful thing to watch is whether the next release arrives in months rather than years; the entries do not indicate what it would contain.
Alternatives to discretetests and Fail2Ban
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either discretetests or Fail2Ban.
portfoliobacktest
Four dormant years end with a test fix, not a feature
medicalcoder
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
Dragonfly
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
Unleash
Three kill-switch explainers to one point release — Unleash's feed is content-led, not release-led.
Jackett
Jackett's daily release treadmill now spends commits undoing tracker removals it made days earlier.
See all discretetests alternatives → · See all Fail2Ban alternatives →
Recent activity from discretetests and Fail2Ban
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoFail2Ban1.1.1 final lands with systemd socket activation
- 2mo agodiscretetestsSign tests and a pluggable permutation test
- 2mo agodiscretetestsInput observation names carried through results
- 2mo agodiscretetestsWilcoxon, Mann-Whitney and homogeneity tests join the package
- 2mo agodiscretetestsmacOS compilation fix
- 1y agoFail2Ban1.1.1 beta, superseded 14 months later by the final
- 2y agoFail2Ban1.1.0 restores Python 3.12 and 3.13 compatibility
- 3y agoFail2Ban1.0.2 fixes a Dovecot filter regression
- 3y agoFail2Ban1.0.1 rolls up filter and action updates
- 5y agoFail2Ban0.11.2 stability and filter updates
Frequently asked questions
What is the difference between discretetests and Fail2Ban?
They serve adjacent needs but don't currently overlap on shipped themes. Fail2Ban is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is discretetests better than Fail2Ban?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fail2Ban is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to discretetests?
Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.
What are the best alternatives to Fail2Ban?
Top Fail2Ban alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fail2Ban alternatives" section above for the current picks, or visit /alternatives/fail2ban for the full list with editorial commentary on each.