0

/ 100

GradeD

Early stage. Tests, CI, and a strong README would raise this score quickly.

Top 50% of 5,156 graded repos

Firebird server, client and tools

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (73).

See your top fixes
Now
D
66
Potential
C
73

Top fixes

Highest-impact changes first, ranked by point weight

17 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

62

Install and run instructions9pt0

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

Add a section showing how to install dependencies.

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt85

README is present.

License6pt100

A license file is present.

Engineering

65

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.

Reproducibility6pt10

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 (android/embedded/src/androidTest/java/org/firebirdsql/android/embedded/ExampleInstrumentedTest.kt).

CI/CD14pt85

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

73

Repository metadata5pt60

Repository has a description.

Activity5pt60

Last pushed 3-6 months ago (−40 pts). A push within 90 days earns 80 pts; within 30 days earns 100 pts.

A recent commit keeps the project looking alive to visitors and contributors.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (android/build.gradle).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

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

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files24 root entries
  • .github
    Good: CI is configured (.github/workflows/main.yml).
  • .vscode
  • android
    Good: Test files detected (android/embedded/src/androidTest/java/org/firebirdsql/android/embedded/ExampleInstrumentedTest.kt).
    Good: Dependency manifest found (android/build.gradle).
    Issue: Build artifacts or local files may be committed (android/.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
  • builds
    Good: A license file is present.
    Good: Environment pinned via builds/docker/linux/arm32-arm64/Dockerfile.
  • doc
  • examples
  • extern
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • src
  • vcpkg-custom
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • acx_pthread.m4
  • autogen.sh
  • binreloc.m4
  • CHANGELOG.md
  • CMakeLists.txt
  • configure.ac
  • Makefile.in
  • 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.
    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.
  • setupBuildNum.sh
  • vcpkg
  • 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/rodrigobertozzi/firebird)](https://www.repo-grade.com/report/rodrigobertozzi/firebird)

More graded repos