Hey, Code Rockstars!Look at what you're building!
From that first commit to the hundredth bug fix, every project takes effort, patience and a little bit of madness. And I absolutely love that! So, what's happening under the hood? I look at four key aspects of your repositories to understand their technical health. Come, let me show you what I look for!
The four things I geek out about!
Dependencies
Are your tools up to date?
Every project uses packages and libraries to get things done. I check:
- Are you using outdated versions?
- Are newer versions available?
- Are those packages still maintained?
Maintenance
Are your technologies still going strong?
Technology keeps evolving, and so should the tools behind your projects. I check:
- Are your dependencies actively maintained?
- Are they still supported?
- Have they been discontinued or abandoned?
Compatibility
Is everything working well together?
Your project uses different tools and technologies. They need to work well together. I check:
- Do the versions work with each other?
- Are they compatible with your technology environment?
- Are there any version conflicts?
Structure
Is your project organised well?
A well-organised project makes a difference. I look at:
- How your project files are organised.
- How the code is structured.
- How consistently the repository is arranged.
Four important perspectives. One consolidated TechieDebt score.
That's how I get to know your project's technical health!
A little guide to your score!
Scores run from 1 to 10. Lower is healthier.
1.0–2.0
Excellent
You're doing amazing!
You're doing amazing!
2.1–4.0
Healthy
Looking good! Keep it going.
Looking good! Keep it going.
4.1–6.0
Needs Attention
A little room to grow.
A little room to grow.
6.1–10
High Debt
Every score is a fresh starting point!
Every score is a fresh starting point!
What scoring covers — and what it does not
TechieDebt looks at technology-health signals across dependencies, maintenance, compatibility, and structure. It does not replace a security scanner, code review, or production monitoring, and it does not claim to detect security vulnerabilities.
Scores are a consolidated view of those perspectives so you can compare projects over time and on the public Developers leaderboard. Repository names stay private; you choose which project name is shown.
A little tech talk, shall we?
From JavaScript to Python, Go to Rust, I've got plenty of languages to explore! Here's the list of technologies I currently know how to assess.
- JavaScript / TypeScript
- Python
- Rust
- Go
- Ruby
- Java / Kotlin
- .NET
- PHP
- Dart / Flutter
- Swift / Apple
- Elixir
- Scala
- C / C++
Ready to see where you stand?
Once your paid assessment is complete, I'll put your combined score on the Developers Leaderboard.
You decide which project name gets shown publicly. Your repository names stay private. Always!