orneryd/nornicdb
Grade a repo

90

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 12% of 5,156 graded repos

Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Using Neo4j Bolt/Cypher and qdrant's gRPC means you can switch with no changes while adding intelligent features like schemas, managed embeddings, reranking+llm, GPU accel, Auto-TLP, Policy-based Memory Decay, and MCP server.

Documentation90
Engineering88
Health94
Go820MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  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
    Install and run instructions9pt

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

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

90

Contributing guide5pt55

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

88

CI/CD14pt57

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

Tests18pt100

Test files detected (apoc/atomic/atomic_test.go).

Linting and formatting5pt100

Formatting enforced (gofmt (built into Go toolchain)).

Reproducibility6pt100

Lockfile present (go.sum). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

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

  • 123 / 515
    Commits (30d / 90d)
  • 45
    Forks
  • 58
    Releaseslatest 7mo ago

Community

  • 85% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 820
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 3h
    Median PR merge time
  • 3
    Open issues
Repository files49 root entries
  • .agents
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 4 ecosystems (gomod, npm, github-actions, docker). Dependencies stay current.
    Good: Issue or PR templates present.
  • apoc
    Good: Test files detected (apoc/atomic/atomic_test.go).
  • cmd
  • deploy
  • docker
  • docs
  • generated
  • lib
  • macos
  • models
  • neural
    Issue: Build artifacts or local files may be committed (neural/export/__pycache__/__init__.cpython-314.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • pkg
  • plugins
  • resolvers
  • scripts
  • testing
  • ui
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • build-cuda.bat
  • build.bat
  • build.ps1
  • build.sh
  • CHANGELOG.md
  • CITATION.cff
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • CONTRIBUTORS.md
  • DIY.md
  • docker-compose.amd64.yml
  • docker-compose.arm64.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • env.local
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE.md
    Good: Licensed under MIT.
  • Makefile
  • mkdocs.yml
  • neo4j_import.py
  • nornicdb.example.yaml
  • NOTICES.md
  • PATENTS.md
  • 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.
  • requirements-docs.txt
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
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/orneryd/nornicdb)](https://www.repo-grade.com/report/orneryd/nornicdb)

More graded Go repos