Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 21:31 UTC

swissmakers / fail2ban-ui

Fail2Ban UI is a management platform for operating Fail2Ban across one or more Linux hosts. It provides a central place to review bans, search and unban IP addresses, manage jails and filters, and receive notifications.

Go · JavaScript · HTMLAGPL-3.0★ 345 stars⑂ 37 forkssince Jan 2025View on GitHub ↗
KindLibraryNetwork servicehow this is determined

swissmakers/fail2ban-ui holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on AI Readiness (47/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

77
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

77
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02).

Ownership

Swissmakers GmbHPersonal account
15 followers41 public repossince Jun 2024

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/swissmakers/fail2ban-uiv1.5.4-2418 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

89Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 506 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year506
human_commit_share1
days_since_last_push12
active_weeks_last_year35

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 18 days ago
27/27Release cadence — a release every ~17.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv1.5.4
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases17.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
41.1/60Stars — 345 stars
13/25Forks — 37 forks
3.9/15Watchers — 6 watchers
Inputs used
forks37
stars345
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (AGPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.2/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 13 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.856
How it's scored
37.5/42Issue resolution — 89% of issues closed
29/30PR acceptance — 117/121 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 1/4 approved changesets -- score normalized to 2
Inputs used
merged_prs117
open_issues9
closed_issues75
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.893
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.7/25Owner reach — 15 followers of swissmakers
16.3/25Track record — 41 public repos, account ~2 yr old
Inputs used
followers15
owner_typeUser
is_verified—
owner_loginswissmakers
public_repos41
account_age_days811
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 18 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/swissmakers/fail2ban-ui
ecosystemsgo
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 3 out of 4 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://fail2ban-ui.com
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicsdashboard, fail2ban, golang, linux, webui, fail2ban-dashboard, intrusion-detection, remote-management, fail2ban-ui
has_wikiyes
homepagehttps://fail2ban-ui.com
docs_sitehttps://fail2ban-ui.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.8/2.5CI-Tests — 3 out of 4 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 1/4 approved changesets -- score normalized to 2
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0.5/5SAST — SAST tool is not run on all commits -- score normalized to 1
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
24.7/35Direct dependencies free of known advisories — 2 affected: golang.org/x/crypto v0.52.0 (unknown), golang.org/x/text v0.37.0 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories6
affected_packages3
assessed_packages47
unassessed_packages1
affected_by_severityunknown 3
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 47 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7.5/40Legible commit history — 14 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.14
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
54.5/55Manageable file sizes — 1/115 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes61,441
source_files_sampled115
oversized_source_files1

Key facts

345GitHub stars
13contributors
506commits, last 12 months
12days since last push
23releases
1bus factor
9open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'fail2ban-ui' from its registry

More detail

Star and fork history 0 ★ / 37 ⇿
0Stars
37Forks
23Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

01325383722025-022025-112026-09
Major 0Minor 3Patch 20

Each point covers 2 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-09 21:30 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests3 out of 4 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 1/4 approved changesets -- score normalized to 2
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
1SASTSAST tool is not run on all commits -- score normalized to 1
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Gogithub.com/coreos/go-oidc/v3v3.17.0go.mod
Gogithub.com/elastic/go-grokv0.3.1go.mod
Gogithub.com/gin-gonic/ginv1.11.0go.mod
Gogithub.com/go-playground/validator/v10v10.30.1go.mod
Gogithub.com/gorilla/websocketv1.5.3go.mod
Gogithub.com/likexian/whoisv1.15.7go.mod
Gogithub.com/oschwald/maxminddb-golangv1.13.1go.mod
Gogolang.org/x/cryptov0.52.0go.mod
Gogolang.org/x/oauth2v0.35.0go.mod
Gogolang.org/x/textv0.37.0go.mod
Gomodernc.org/sqlitev1.46.0go.mod
All dependencies 48

Full resolved dependency set from the GitHub dependency graph: 11 direct and 37 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogithub.com/coreos/go-oidc/v3v3.17.0direct
Gogithub.com/elastic/go-grokv0.3.1direct
Gogithub.com/gin-gonic/ginv1.11.0direct
Gogithub.com/go-playground/validator/v10v10.30.1direct
Gogithub.com/gorilla/websocketv1.5.3direct
Gogithub.com/likexian/whoisv1.15.7direct
Gogithub.com/oschwald/maxminddb-golangv1.13.1direct
Gogolang.org/x/cryptov0.52.0direct
Gogolang.org/x/oauth2v0.35.0direct
Gogolang.org/x/textv0.37.0direct
Gomodernc.org/sqlitev1.46.0direct
Gogithub.com/bytedance/gopkgv0.1.3indirect
Gogithub.com/bytedance/sonicv1.15.0indirect
Gogithub.com/bytedance/sonic/loaderv0.5.0indirect
Gogithub.com/cloudwego/base64xv0.1.6indirect
Gogithub.com/dustin/go-humanizev1.0.1indirect
Gogithub.com/gabriel-vasile/mimetypev1.4.13indirect
Gogithub.com/gin-contrib/ssev1.1.0indirect
Gogithub.com/go-jose/go-jose/v4v4.1.4indirect
Gogithub.com/go-playground/localesv0.14.1indirect
Gogithub.com/go-playground/universal-translatorv0.18.1indirect
Gogithub.com/goccy/go-jsonv0.10.5indirect
Gogithub.com/goccy/go-yamlv1.19.2indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/json-iterator/gov1.1.12indirect
Gogithub.com/klauspost/cpuid/v2v2.3.0indirect
Gogithub.com/leodido/go-urnv1.4.0indirect
Gogithub.com/magefile/magev1.15.0indirect
Gogithub.com/mattn/go-isattyv0.0.20indirect
Gogithub.com/modern-go/concurrentv0.0.0-20180306012644-bacd9c7ef1ddindirect
Gogithub.com/modern-go/reflect2v1.0.2indirect
Gogithub.com/ncruces/go-strftimev1.0.0indirect
Gogithub.com/pelletier/go-toml/v2v2.2.4indirect
Gogithub.com/quic-go/qpackv0.6.0indirect
Gogithub.com/quic-go/quic-gov0.59.1indirect
Gogithub.com/remyoudompheng/bigfftv0.0.0-20230129092748-24d4a6f8daecindirect
Gogithub.com/twitchyliquid64/golang-asmv0.15.1indirect
Gogithub.com/ugorji/go/codecv1.3.1indirect
Gogo.uber.org/mockv0.6.0indirect
Gogolang.org/x/archv0.24.0indirect
Gogolang.org/x/expv0.0.0-20260212183809-81e46e3db34aindirect
Gogolang.org/x/netv0.55.0indirect
Gogolang.org/x/sysv0.45.0indirect
Gogoogle.golang.org/protobufv1.36.11indirect
Gomodernc.org/libcv1.68.0indirect
Gomodernc.org/mathutilv1.7.1indirect
Gomodernc.org/memoryv1.11.0indirect
npmtailwindcss^3.4.19indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 47 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 2 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/cryptov0.52.0directunknown40.56.0
golang.org/x/textv0.37.0directunknown10.39.0
golang.org/x/netv0.55.0indirectunknown11.27.0-rc.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go.