repowisebinwiederhier/ntfy

Code health of binwiederhier/ntfy

Repowise scores binwiederhier/ntfy at 7.5 out of 10 for code health, which reads as good, alongside maintainability 8.0 and static performance 9.5 on the same scale. There are 914 open findings across the three pillars, and the lowest-scoring file is server_account.go at 2.0. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.

Findings by severity

70 critical, 157 high, 316 medium, 362 low.

Hotspots

46 files are flagged as hotspots. The top 5:

  • server/server_test.go: 17 commits in the last 90 days from 11 contributors with 3 recent bug fixes
  • user/manager.go: 4 commits in the last 90 days from 6 contributors with 1 recent bug fix
  • server/server.go: 35 commits in the last 90 days from 14 contributors with 3 recent bug fixes
  • user/manager_test.go: 10 commits in the last 90 days from 6 contributors with 2 recent bug fixes
  • message/cache.go: 35 commits in the last 90 days from 1 contributor with 4 recent bug fixes

Lowest-scoring files

  • server/server_account.go: 2.0 out of 10 with 1 bug fix in the last 180 days
  • server/server.go: 2.5 out of 10 with 3 bug fixes in the last 180 days
  • cmd/serve.go: 2.5 out of 10 with 1 bug fix in the last 180 days
  • docs/static/js/config-generator.js: 2.5 out of 10
  • server/server_payments.go: 3.8 out of 10 with 1 bug fix in the last 180 days

Checked against bug fixes

Of the 20 files Repowise scores lowest, 13 had a bug fix in the last 180 days. Across all 345 scored files, 17.7% had a bug fix in that window.

Dead code and refactoring

Repowise found 14 unused exports. 17 refactoring targets across 17 files would raise the score.

More on ntfy: summary and FAQ, codebase overview, architecture.