Breakdown

• Docs

  23 / 25

  • Passed:README present6/6
  • Partly earned:README has real depth6/8
  • Passed:Repository description set5/5
  • Passed:Topics tagged4/4
  • Passed:Homepage or docs link2/2

• Community

  17 / 20

  • Passed:LICENSE file present8/8
  • Passed:Contributing guide4/4
  • Passed:Code of conduct3/3
  • Not earned:Security policy0/3
  • Passed:Issue or PR templates2/2

• Activity

  20 / 20

  • Passed:Pushed recently10/10
  • Passed:Commit cadence over 90 days6/6
  • Passed:Issue backlog in proportion4/4

• Popularity

  15 / 15

  • Passed:Stars11/11
  • Passed:Forks4/4

• Hygiene

  20 / 20

  • Passed:CI workflows configured8/8
  • Passed:Not archived4/4
  • Passed:Original, not a fork3/3
  • Passed:Issues enabled3/3
  • Passed:Language detected2/2

What to fix

1. Add SECURITY.md so vulnerability reports reach you privately instead of a public issue.

   +3

2. Expand the README: what the project does, how to install it, and one worked example.

   +2

Put it in your README

• Card[![GitCheckup](https://gitcheckup.com/api/og?repo=vercel/next.js)](https://gitcheckup.com/r/vercel/next.js)Copy
• Badge[![GitCheckup](https://gitcheckup.com/api/badge?repo=vercel/next.js)](https://gitcheckup.com/r/vercel/next.js)Copy