ladybugdb/ladybug
Grade a repo

0

/ 100

GradeC

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

LadybugDB a graph database

Documentation85
Engineering67
Health100
C++1,362MITtoday

Documentation

85

Contributing guide5pt61

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.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

67

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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 (test).

CI/CD14pt85

CI is configured (.github/workflows/build-and-deploy-extension.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (scripts/pip-package/setup.cfg).

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)
  • 106
    Forks
  • 15
    Releaseslatest 2mo ago

Community

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

Responsiveness

  • 17d 19h
    Median issue response
  • 4h
    Median PR merge time
  • 64
    Open issues
Repository files29 root entries
  • .github
    Good: CI is configured (.github/workflows/build-and-deploy-extension.yml).
    Good: Environment pinned via .github/docker/ubuntu-22.04-gcc13/Dockerfile.
    Good: Issue or PR templates present.
  • cmake
  • docs
  • examples
  • logo
  • scripts
    Good: Dependency manifest found (scripts/pip-package/setup.cfg).
  • security
  • src
  • test
    Good: Test files detected (test).
  • third_party
  • tools
  • .clang-format
  • .clang-format-ignore
  • .clang-tidy
  • .clang-tidy-analyzer
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .lcovrc
  • AGENTS.md
  • benchmark
  • CMakeLists.txt
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • dataset
  • extension
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • pixi.toml
  • 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.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.