Soundings for open-source dependencies

# Should you depend on this repo?

RepoRadar reads a public GitHub repo's activity, its packages and its advisories, then gives a plain verdict with the reasons.

Try `owner/repo`, a GitHub URL, `npm:express` or `pypi:requests`. Choosing between two? [Compare them side by side](https://reporadar.ai/-/compare).

**Shortcut:** on any GitHub repo page, swap `github.com` for `reporadar.ai` in the address bar to get its report.

github.com/expressjs/express↓[**reporadar.ai**/expressjs/express](https://reporadar.ai/expressjs/express)

![Engraved sea chart: a lighthouse beam sweeps across islands and depth lines.](https://reporadar.ai/art/hero-plate-1024.webp)

Plate IChart of the dependency seas

## Example verdicts

Recent readings

- [alikon-art/DeterminFlow](https://reporadar.ai/alikon-art/DeterminFlow) Caution One person wrote most of the recent commits.
- [microg/GmsCore](https://reporadar.ai/microg/GmsCore) Healthy Actively maintained by 46 people, no known risks.
- [SeeRay11/OpenFlow](https://reporadar.ai/SeeRay11/OpenFlow) Caution One person wrote most of the recent commits.

## What every report checks

[How it works](https://reporadar.ai/methodology)

1. **Maintenance**Human commits, releases, how fast pull requests merge and whether issues get a reply.
2. **People**How many people the work rests on, and whether that changed.
3. **Stars**Weekly star history, unexplained bursts and stars GitHub has since removed.
4. **Risk**License changes, published packages, known advisories and named successors.

New study

## Stars GitHub later removed

What do unexplained star bursts look like across GitHub, and how often do stars disappear later? We report the aggregates.

[Read the study](https://reporadar.ai/-/study/removed-stars)

Source: https://reporadar.ai/