cucumber/cucumber-jvm
Grade a repo

70

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Top 46% of 5,156 graded repos

Cucumber for the JVM

Documentation74
Engineering56
Health100
Java2,821MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

18 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

74

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

56

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt57

CI is configured (.github/workflows/test-java.yaml).

Tests18pt80

Test files detected (compatibility/src/test).

Linting and formatting5pt100

Java/Kotlin linting configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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

  • 24 / 71
    Commits (30d / 90d)
  • 2,012
    Forks
  • 48
    Releaseslatest 3y ago

Community

  • 87% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 2,821
    Watchers

Responsiveness

  • 2d 11h
    Median issue response
  • 1d 4h
    Median PR merge time
  • 51
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/test-java.yaml).
  • .mvn
  • .revapi
  • .spotless
  • compatibility
    Good: Test files detected (compatibility/src/test).
  • cucumber-archetype
  • cucumber-bom
  • cucumber-core
  • cucumber-gherkin
  • cucumber-gherkin-messages
  • cucumber-guice
  • cucumber-jakarta-cdi
  • cucumber-jakarta-openejb
  • cucumber-java
  • cucumber-java8
  • cucumber-junit
  • cucumber-junit-platform-engine
  • cucumber-kotlin-java8
  • cucumber-picocontainer
  • cucumber-plugin
  • cucumber-spring
  • cucumber-testng
  • datatable
  • datatable-matchers
  • docstring
  • release-notes
  • .editorconfig
    Good: Java/Kotlin linting configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under MIT.
  • mvnw
  • mvnw.cmd
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • RELEASING.md
  • SEMVER.md
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/cucumber/cucumber-jvm)](https://www.repo-grade.com/report/cucumber/cucumber-jvm)

More graded Java repos