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

High-performance embedded graph database for analytics and real-time transactions

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt99

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.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

66

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.

CI/CD14pt57

CI is configured (.github/workflows/build-extensions.yml).

Reproducibility6pt70

Lockfile present (examples/ldbc_interactive_benchmark/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (extension/httpfs/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (examples/ldbc_interactive_benchmark/requirements.txt).

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)
  • 27
    Forks
  • 1
    Releaseslatest 28d ago

Community

  • Community health
  • authors own >50% of commits
  • 114
    Watchers

Responsiveness

  • 4d 12h
    Median issue response
  • 11h
    Median PR merge time
  • 94
    Open issues
Repository files42 root entries
  • .cursor
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/build-extensions.yml).
    Good: Issue or PR templates present.
  • .specify
  • benchmark
  • bin
  • cmake
  • doc
  • docker
  • example_dataset
  • examples
    Good: Lockfile present (examples/ldbc_interactive_benchmark/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (examples/ldbc_interactive_benchmark/requirements.txt).
  • extension
    Good: Test files detected (extension/httpfs/tests).
  • img
  • include
  • pre-commit
  • proto
  • scripts
  • skills
  • specs
  • src
  • tests
  • third_party
  • tools
  • .clang-format
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • AGENTS.md
  • CLAUDE.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • dev_and_test.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • NEUG_VERSION
  • neug-config-version.in.cmake
  • neug-config.in.cmake
  • NOTICE.txt
  • 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.
    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.
  • THIRD_PARTY_LICENSES.md