react/react-native
Grade a repo

89

/ 100

GradeB

A landmark open source project with strong engineering quality.

Top 14% of 5,156 graded repos

A framework for building native applications using React

Documentation77
Engineering96
Health89
C++126,071MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  2. 2
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

77

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt65

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

96

Reproducibility6pt70

Lockfile present (Gemfile.lock). Installs are reproducible.

Tests18pt100

Test files detected (.github/workflow-scripts/__tests__).

CI/CD14pt100

CI is configured (.github/workflows/check-for-reproducer.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 192 / 645
    Commits (30d / 90d)
  • 25,178
    Forks
  • 463
    Releaseslatest 11y ago

Community

  • 75% - Good
    Community health
  • 13 bus factor
    authors own >50% of commits
  • 126,071
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 19h
    Median PR merge time
  • 1,046
    Open issues
Repository files41 root entries
  • __docs__
  • .bundle
  • .github
    Good: Test files detected (.github/workflow-scripts/__tests__).
    Good: CI is configured (.github/workflows/check-for-reproducer.yml).
    Good: Issue or PR templates present.
  • flow-typed
  • gradle
  • jest
  • packages
  • private
  • scripts
  • .babelrc
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore
  • .eslintrc.js
  • .flowconfig
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint-cli2.mjs
  • .prettierignore
  • .prettierrc.js
  • build.gradle.kts
  • CHANGELOG-0.5x.md
  • CHANGELOG-0.6x.md
  • CHANGELOG-0.7x.md
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • ECOSYSTEM.md
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • gradle.properties
  • gradlew
  • gradlew.bat
  • jest.config.js
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • react-native.code-workspace
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • runXcodeTests.sh
  • settings.gradle.kts
  • yarn.lock
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/react/react-native)](https://www.repo-grade.com/report/react/react-native)

More graded C++ repos