75

/ 100

GradeC

Popular and well-maintained. A little polish away from elite status.

Top 39% of 5,156 graded repos

Truly independent web browser

C++64,514BSD-2-Clause1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

21 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

49

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

README12pt55

README is present.

Contributing guide5pt64

Contributing guide is detailed and thorough.

License6pt100

Licensed under BSD-2-Clause.

Engineering

88

CI/CD14pt57

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

Tests18pt100

Test files detected (Libraries/LibWasm/Tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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

  • 703 / 3062
    Commits (30d / 90d)
  • 3,082
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 8 bus factor
    authors own >50% of commits
  • 64,514
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 6h
    Median PR merge time
  • 509
    Open issues
Repository files39 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/fedora-ci/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/ci-image.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, rust-toolchain). Dependencies stay current.
    Good: Issue or PR templates present.
  • AK
  • Base
  • Documentation
  • Libraries
    Good: Test files detected (Libraries/LibWasm/Tests).
  • Meta
  • Services
  • Tests
  • UI
  • Utilities
  • .clang-format
  • .clang-tidy
  • .clangd
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gdbinit
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lldbinit
  • .mailmap
  • .pre-commit-config.yaml
  • .prettierignore
  • .prettierrc
  • .ycm_extra_conf.py
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CMakeLists.txt
  • CMakePresets.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
  • ISSUES.md
  • LICENSE
    Good: Licensed under BSD-2-Clause.
  • pyproject.toml
  • 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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rust-toolchain.toml
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.
  • vcpkg-configuration.json
  • vcpkg.json
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/ladybirdbrowser/ladybird)](https://www.repo-grade.com/report/ladybirdbrowser/ladybird)

More graded C++ repos