yetone/magpie

Code health of yetone/magpie

Repowise scores yetone/magpie at 6.4 out of 10 for code health, which reads as fair, alongside maintainability 6.4 and static performance 9.3 on the same scale. There are 37,188 open findings across the three pillars, and the lowest-scoring file is gateway.go at 1.0. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.

Findings by severity

1,970 critical, 4,482 high, 14,216 medium, 16,520 low.

Hotspots

112 files are flagged as hotspots. The top 5:

internal/gui/assets/app.js: 80 commits in the last 90 days from 1 contributor with 1 recent bug fix
internal/gui/assets/i18n.js: 78 commits in the last 90 days from 1 contributor with 1 recent bug fix
internal/gui/assets/plugins/library/client.js: 18 commits in the last 90 days from 1 contributor
internal/provider/codex_projects.go: 3 commits in the last 90 days from 1 contributor
site/worker.js: 4 commits in the last 90 days from 1 contributor

Lowest-scoring files

internal/gateway/gateway.go: 1.0 out of 10 with 1 bug fix in the last 180 days
internal/gui/assets/app.js: 1.0 out of 10 with 1 bug fix in the last 180 days
internal/gateway/claude_subscription.go: 1.0 out of 10
internal/gui/assets/plugins/routing/client.js: 1.0 out of 10
internal/gateway/codex_backend.go: 1.0 out of 10

Checked against bug fixes

Of the 20 files Repowise scores lowest, 4 had a bug fix in the last 180 days. Across all 7,659 scored files, 0.4% had a bug fix in that window.

Dead code and refactoring

Repowise found 14 unused exports. 2,443 refactoring targets across 2,443 files would raise the score.

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