apache/solr
Grade a repo

0

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 12% of 5,156 graded repos

Apache Solr open-source search software

Documentation91
Engineering86
Health100
Java1,628Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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 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

91

Contributing guide5pt59

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

86

Tests18pt80

Test files detected (solr/api/src/test).

Reproducibility6pt80

Lockfile present (dev-tools/scripts/requirements.txt). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/tests-via-crave.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (build.gradle).

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

  • -
    Commits (30d / 90d)
  • 837
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,628
    Watchers

Responsiveness

  • -
    Median issue response
  • 11d 21h
    Median PR merge time
  • 283
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/tests-via-crave.yml).
    Good: Issue or PR templates present.
  • build-tools
  • changelog
  • dev-docs
  • dev-tools
    Good: Lockfile present (dev-tools/scripts/requirements.txt). Installs are reproducible.
  • gradle
  • kotlin-js-store
  • platform
  • solr
    Good: Test files detected (solr/api/src/test).
    Good: Environment pinned via solr/docker/example/docker-compose.yml.
  • .asf.yaml
  • .editorconfig
    Good: Java/Kotlin linting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • build.gradle
    Good: Dependency manifest found (build.gradle).
  • CHANGELOG.md
  • 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.
  • gradle.lockfile
  • gradlew
  • gradlew.bat
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • NOTICE.txt
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • settings-gradle.lockfile
  • settings.gradle
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/apache/solr)](https://www.repo-grade.com/report/apache/solr)

More graded Java repos