ducktors/turborepo-remote-cache

Code health of ducktors/turborepo-remote-cache

Repowise scores ducktors/turborepo-remote-cache at 8.4 out of 10 for code health, which reads as good, alongside maintainability 8.6 and static performance 9.9 on the same scale. There are 90 open findings across the three pillars, and the lowest-scoring file is jwt.ts at 5.8. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.

Findings by severity

11 critical, 27 high, 25 medium, 27 low.

Hotspots

8 files are flagged as hotspots. The top 5:

test/jwt-auth.ts: 3 commits in the last 90 days from 3 contributors with 3 recent bug fixes
test/body-limit.ts: 3 commits in the last 90 days from 2 contributors with 3 recent bug fixes
test/azure-blob-storage.ts: 5 commits in the last 90 days from 6 contributors with 6 recent bug fixes
test/gcs-publication.ts: 3 commits in the last 90 days from 2 contributors with 3 recent bug fixes
src/plugins/remote-cache/storage/index.ts: 5 commits in the last 90 days from 17 contributors with 7 recent bug fixes

Lowest-scoring files

src/plugins/remote-cache/auth/jwt.ts: 5.8 out of 10 with 4 bug fixes in the last 180 days
src/plugins/remote-cache/routes/head-artifact.ts: 6.2 out of 10 with 8 bug fixes in the last 180 days
src/plugins/remote-cache/routes/get-artifact.ts: 6.2 out of 10 with 7 bug fixes in the last 180 days
src/plugins/remote-cache/storage/index.ts: 6.2 out of 10 with 7 bug fixes in the last 180 days
src/plugins/remote-cache/routes/put-artifact.ts: 6.3 out of 10 with 6 bug fixes in the last 180 days

Checked against bug fixes

Of the 20 files Repowise scores lowest, 10 had a bug fix in the last 180 days. Across all 57 scored files, 17.5% had a bug fix in that window.

Dead code and refactoring

3 refactoring targets across 3 files would raise the score.

More on turborepo-remote-cache: summary and FAQ, codebase overview, architecture.