CodeIssuesPull RequestsActionsSecurityInsights
✨ AI
More
Settings
C
61/100
Health score

Insights

No security issues detected — clean codebase
No tests found — adding tests would significantly improve code reliability
No LICENSE file — open source projects need a license to be usable
No activity in 90+ days — project may be dormant
How to improve this score61 → 81 possible
Gains are computed from the same formula that produced the score — completing everything below is worth 20 points.
+10
1. Add a test suite — any tests at all move the score off zerotesting
0 test files today against ~20 source files (None)
Fix it yourself

Change: Add a test suite — any tests at all move the score off zero

0 test files today against ~20 source files (None)

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

+4.5
2. Push again — freshness decays the scoreactivity
Last push 138 days ago; pushing within 7 days is worth 30 of activity's 100 points
Fix it yourself

Change: Push again — freshness decays the score

Last push 138 days ago; pushing within 7 days is worth 30 of activity's 100 points

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

+2
3. Add a LICENSE filedocumentation
Unlicensed code is legally unusable by anyone else
Fix it yourself

Change: Add a LICENSE file

Unlicensed code is legally unusable by anyone else

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

+1.5
4. Add CONTRIBUTING.mddocumentation
Tells collaborators how to work on the repo
Fix it yourself

Change: Add CONTRIBUTING.md

Tells collaborators how to work on the repo

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

+1.5
5. Add a CHANGELOGdocumentation
Lets users see what changed between versions
Fix it yourself

Change: Add a CHANGELOG

Lets users see what changed between versions

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

+0.8
6. Split the largest files to bring average size under 2,000 bytescomplexity
Average is 3,113 bytes across 20 files; start with page.tsx, page.tsx, page.tsx
Fix it yourself

Change: Split the largest files to bring average size under 2,000 bytes

Average is 3,113 bytes across 20 files; start with page.tsx, page.tsx, page.tsx

Make the change on a branch, push it, and open a pull request — the health score recomputes on the next visit.

Security100
25 of 25 possible overall points (weight 25%)
0 findings across 0 rules
0 critical · 0 high · 0 medium
Testing0
0 of 20 possible overall points (weight 20%)
No tests found
Coverage estimate: None
Complexity90
14 of 15 possible overall points (weight 15%)
20 source files
Avg file size: 3,113 bytes
Largest: page.tsx (14,776 bytes)
Dependencies100
15 of 15 possible overall points (weight 15%)
11 dependencies (package.json)
Lockfile present
Documentation46
5 of 10 possible overall points (weight 10%)
README found
No license
3 doc files
Activity20
3 of 15 possible overall points (weight 15%)
0 commits (30d)
3 contributors
Last push: 138d ago
Zero-config CIAuto-detected · Node.js project detected · TypeScript detected · Next.js framework · React
Type check
npx tsc --noEmit
Lint
npm run lint
Build
npm run build
Type check
npm run typecheck