wdaqua/qanary
Grade a repo

75

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 39% of 5,156 graded repos

Qanary a methodology to construct and share resources to build QA systems

Documentation69
Engineering72
Health94
Java631mo 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
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    License6pt

    Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

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

69

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

72

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.

Reproducibility6pt30

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (qald-evaluator/src/test).

CI/CD14pt100

CI is configured (.github/workflows/dependency-check.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (lint step in CI workflow).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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

  • -
    Commits (30d / 90d)
  • 26
    Forks
  • 4
    Releaseslatest 1mo ago

Community

  • 50% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 63
    Watchers

Responsiveness

  • 2d 23h
    Median issue response
  • 9h
    Median PR merge time
  • 11
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/dependency-check.yml).
    Good: Dependabot covers 3 ecosystems (github-actions, maven, docker). Dependencies stay current.
  • doc
  • frontend-e2e
  • qald-evaluator
    Good: Test files detected (qald-evaluator/src/test).
  • qanary_commons
  • qanary_component-archetype
  • qanary_component-parent
  • qanary_component-template
  • qanary_pipeline-client
  • qanary_pipeline-template
  • service_config
  • .env
    Issue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .gitleaksignore
  • BUILDING.md
  • CITATION.cff
  • 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.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • 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.
    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.
  • 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/wdaqua/qanary)](https://www.repo-grade.com/report/wdaqua/qanary)

More graded Java repos