antflydb/antfly
Grade a repo

0

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 24% of 5,156 graded repos
Documentation93
Engineering78
Health84
Zig400Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 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
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Issue and PR templates6pt

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

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

93

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

78

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.

Tests18pt80

Test files detected (examples/docsaf/entity/config_test.go).

Reproducibility6pt80

Lockfile present (examples/docsaf/go.sum). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/antfly-go.yml).

Linting and formatting5pt100

Linter or formatter configured (.golangci.yaml).

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (examples/antfly-lite-go/go.mod).

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)
  • 26
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 14h
    Median issue response
  • 5h
    Median PR merge time
  • 4
    Open issues
Repository files32 root entries
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/antfly-go.yml).
  • configs
  • devops
    Good: Environment pinned via devops/docker-compose-s3/docker-compose.yml.
  • docs
  • examples
    Good: Test files detected (examples/docsaf/entity/config_test.go).
    Good: Lockfile present (examples/docsaf/go.sum). Installs are reproducible.
    Good: Dependency manifest found (examples/antfly-lite-go/go.mod).
  • extensions
  • go
  • py
  • rs
  • scripts
  • specs
  • ts
  • work-log
  • zig
  • .dockerignore
  • .gcloudignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .golangci.yaml
    Good: Linter or formatter configured (.golangci.yaml).
  • CHANGELOG.md
  • CLAUDE.md
  • cloudbuild.yaml
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    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.
  • DERIVED_DOCUMENT_HIERARCHY.md
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • openapi.yaml
  • quickstart.tape
  • 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.
  • RELEASE.md
  • wikipedia-config.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/antflydb/antfly)](https://www.repo-grade.com/report/antflydb/antfly)

More graded Zig repos