biomejs/biome
Grade a repo

0

/ 100

GradeA

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

A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.

Documentation93
Engineering96
Health79
Rust25,187Apache-2.0today

Documentation

93

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

96

Reproducibility6pt70

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

Tests18pt100

Test files detected (crates/biome_cli/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 196 / 923
    Commits (30d / 90d)
  • 1,047
    Forks
  • 147
    Releaseslatest 2y ago

Community

  • 87% - Good
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 25,187
    Watchers

Responsiveness

  • 6d 11h
    Median issue response
  • 2h
    Median PR merge time
  • 496
    Open issues
Repository files43 root entries
  • .cargo
  • .changeset
  • .claude
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/lint_rule_docs.yml).
    Good: Issue or PR templates present.
  • crates
    Good: Licensed under Apache-2.0.
    Good: Test files detected (crates/biome_cli/tests).
    Issue: Build artifacts or local files may be committed (crates/biome_js_analyze/tests/specs/correctness/noPrivateImports/node_modules/external-package) (−40 pts).Fix: Remove them and add to .gitignore.
  • e2e-tests
  • fuzz
  • packages
  • plugins
  • scripts
  • xtask
  • .biome.json
  • .coderabbit.yaml
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.json
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG_v1.md
  • CHANGELOG.md
  • CLAUDE.md
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • deny.toml
  • GOVERNANCE.md
  • insta.yml
  • justfile
  • LICENSE-APACHE
  • LICENSE-MIT
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • 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.
  • RELEASES.md
  • rust-toolchain.toml
  • rustfmt.toml
  • tombi.toml