Currently, Proofolio generates a single DevScore, but users do not get a clear explanation of how the score is calculated.
This issue proposes implementing a DevScore Breakdown System, where the final score is composed of multiple weighted components.
Proposed components
GitHub activity (repos, commits, consistency)
LinkedIn/profile completeness
Project quality signals (README, live demo, tech stack)
Contribution diversity (solo vs collaborative work)
Deliverables
A structured score object (TypeScript interface)
UI section showing category-wise scores
Tooltips explaining how each metric affects the final score
Why this is valuable
Improves trust and transparency
Makes feedback actionable
Core product improvement, not cosmetic
Currently, Proofolio generates a single DevScore, but users do not get a clear explanation of how the score is calculated.
This issue proposes implementing a DevScore Breakdown System, where the final score is composed of multiple weighted components.
Proposed components
GitHub activity (repos, commits, consistency)
LinkedIn/profile completeness
Project quality signals (README, live demo, tech stack)
Contribution diversity (solo vs collaborative work)
Deliverables
A structured score object (TypeScript interface)
UI section showing category-wise scores
Tooltips explaining how each metric affects the final score
Why this is valuable
Improves trust and transparency
Makes feedback actionable
Core product improvement, not cosmetic