opensourcecheck Coming soon

Coming soon

Is that open source project as healthy as it looks?

Stars tell you a project is liked. Open Source Check tells you whether it is maintained, understood and safe to build on: who is behind it, whether it is one person or a team, whether the code is sound or a mess, and whether security is reviewed or just assumed.

Reports are not live yet. Search any project to see what its page will hold.

One score, and the reasons behind it

Every project gets a score out of 100, built from eight areas you can open up one by one.

example/project Example report · made-up numbers
66/ 100

Solid code, but it rests on one person.

  • Maintainers & bus factor 22 22 out of 100
  • Activity & release rhythm 81 81 out of 100
  • Community depth 38 38 out of 100
  • Code quality 74 74 out of 100
  • Tests & automation 86 86 out of 100
  • Security practice 55 55 out of 100
  • Documentation 79 79 out of 100
  • Licence & governance 92 92 out of 100

What we check

The questions you would ask before depending on a project, answered from its history rather than its popularity. The charts below use made-up numbers.

Who actually maintains it

81% of last year's commits came from one person

One maintainer or a real team? We measure how the work is spread, and what happens to the project if its busiest person stops.

Liked, or understood

48.2kstars
3people who have changed the core

Plenty of projects are widely starred and barely understood. We count who reviews, who fixes and who could take over, not who clicked.

Still alive

−86% commits, last quarter against the year before

Release rhythm, response time on issues and whether activity is steady, bursty or quietly fading out.

Properly coded, or a mess

  • Tests run on every changeyes
  • Changes reviewed before merge72%
  • Files nobody dares touch14
  • Dependencies years out of date9

Structure, test coverage, review habits and the corners where complexity has piled up.

Security, reviewed or assumed

  • Security policy publishedyes
  • Independent auditnone
  • Median time to fix a report41 days
  • Signed releasesyes

Whether vulnerabilities have a way in, how fast they are fixed and whether anyone outside the project has ever looked.

Who is behind it

  • LicenceApache-2.0
  • Organisations contributing1
  • Fundingdonations
  • Documented way to hand overno

Licence, governance and funding: who decides, who pays and what stops the project changing terms overnight.

Deep-dive analytics

The score is the summary. Behind it sits every measurement, with the evidence it came from.

  • Every number links to the commits, issues and files it was read from
  • History, so you can see a project improving or sliding, not just where it stands today
  • Projects side by side, for when you are choosing between two libraries

78 → 66 over twelve months

A badge for your README or website

Show the score where your users look first. The badge updates itself whenever the project is checked again.

open source check: 91 · Aopen source check91 · A open source check: 66 · Bopen source check66 · B open source check: 34 · Dopen source check34 · D open source check: pendingopen source checkpending

Examples. Until reports launch, every badge reads pending, so you can add yours today and it fills in by itself.

Markdown
[![Open Source Check](https://opensourcecheck.com/badge/your-project.svg)](https://opensourcecheck.com/check?q=your-project)
HTML
<a href="https://opensourcecheck.com/check?q=your-project"><img src="https://opensourcecheck.com/badge/your-project.svg" alt="Open Source Check"></a>