Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Track technical debt score across the board🏦

Open Beginner friendly
#666 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, react, tailwindcss

Research direction

Start in client/src/pages/Dashboard.jsx and trace how tasks are loaded and how the navbar is rendered. Use the supplied tag, status, and priority rules to calculate the debt score and display its level and count. Done when unfinished debt-tagged tasks contribute the expected score and the navbar reflects the result.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Track technical debt score across the board🏦

File: client/src/pages/Dashboard.jsx

No visibility of tech debt accumulating 💀
Tasks tagged "tech-debt" get ignored fr!!

Fix: calculate debt score:
const calculateDebtScore = () => {
const debtTasks = tasks.filter(t =>
t.tags?.some(tag =>
['tech-debt', 'refactor',
'hack', 'fixme', 'legacy']
.includes(tag.toLowerCase())
) && t.status !== 'done'
)

const score = debtTasks.reduce((acc, t) => {
const weight = t.priority === 'high' ? 3
: t.priority === 'medium' ? 2 : 1
return acc + weight
}, 0)

const level = score === 0 ? 'clean'
: score < 5 ? 'manageable'
: score < 10 ? 'concerning'
: 'critical'

return { score, level, count: debtTasks.length }
}

const debt = calculateDebtScore()

// show in navbar:
{debt.count > 0 && (

🏦 debt: {debt.score} )}
Dominant language
JavaScript
Stars
39
Forks
105
Avg merge
21h 41m
Merged PRs (30d)
49

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anoopcodehack/DevBoard

All issues in anoopcodehack/DevBoard

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.