emscripten-core/emscripten
Grade a repo

73

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 22% of 5,156 graded repos

Emscripten: An LLVM-to-WebAssembly Compiler

Documentation85
Engineering79
Health100
C++27,478Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

85

Contributing guide5pt47

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Tests18pt80

Test files detected (test).

Reproducibility6pt90

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

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

  • 137 / 480
    Commits (30d / 90d)
  • 3,529
    Forks
  • 3
    Releaseslatest 1mo ago

Community

  • 75% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 27,478
    Watchers

Responsiveness

  • 10h
    Median issue response
  • 19h
    Median PR merge time
  • 2,471
    Open issues
Repository files49 root entries
  • .circleci
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • cmake
  • docs
  • html
  • media
  • site
  • src
  • system
  • test
    Good: Test files detected (test).
  • third_party
  • tools
  • .clang-format
  • .clang-format-ignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .prettierrc.yml
  • .style.yapf
  • AUTHORS
  • bootstrap.py
  • ChangeLog.md
  • 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.
  • em-config.py
  • em++.py
  • emar.py
  • embuilder.py
  • emcc.py
  • emcmake.py
  • emconfigure.py
  • emmake.py
  • emranlib.py
  • emrun.py
  • emscan-deps.py
  • emscons.py
  • emscripten-version.txt
  • emsize.py
  • emstrip.py
  • eslint.config.mjs
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pyproject.toml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-dev.txt
  • SECURITY.md
    Good: Security policy present.
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/emscripten-core/emscripten)](https://www.repo-grade.com/report/emscripten-core/emscripten)

More graded C++ repos