ccantynz/vapron-starter-static
CodeIssuesPull RequestsActionsSecurityInsights
✨ AI
Understand
Explain codebaseAsk AIChat with repoClaude sessionsNL searchSemantic searchArchaeologyDebt mapDocs tracking
Build
Spec to PRWorkspaceGenerate testsPropose migrationDev environmentCodebase migrator
Ship
Preview URLsAI release notesAI changelog
More
Repository
CommitsBranchesTagsReleasesPackagesSymbolsStale branches
Planning
MilestonesProjectsDiscussionsWikiContributors
Delivery
GatesMerge queueMerge checksDeploymentsPipelineAgents
Activity
Health reportPulsePush log
Settings
C
55/100
Health score

Insights

No security issues detected — clean codebase
No tests found — adding tests would significantly improve code reliability
No dependency manifest found — the Dependencies category is excluded from the score rather than counted as perfect
No LICENSE file — open source projects need a license to be usable
Single contributor — consider inviting collaborators for code review
How to improve this score55 → 75 possible
Gains are computed from the same formula that produced the score — completing everything below is worth 20 points.
+11.8
1. Add a test suite — any tests at all move the score off zerotesting
0 test files today against ~1 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 ~1 source files (None)

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

+2.4
2. 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.8
3. 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.8
4. 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.

+1.8
5. Push again — freshness decays the scoreactivity
Last push 43 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 43 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.

Security100
29 of 29 possible overall points (weight 29%)
0 findings across 0 rules
0 critical · 0 high · 0 medium
Testing0
0 of 24 possible overall points (weight 24%)
No tests found
Coverage estimate: None
Complexity100
18 of 18 possible overall points (weight 18%)
1 source files
Avg file size: 200 bytes
Largest: script.js (200 bytes)
Dependencies—
Not counted in the overall score
No dependency manifest found
Excluded from the score — not counted as perfect
Documentation42
5 of 12 possible overall points (weight 12%)
README found
No license
1 doc files
Activity15
3 of 18 possible overall points (weight 18%)
0 commits (30d)
1 contributors
Last push: 43d ago