layr-labs/d-inferenceNew scan
96/ 100 · A

Polished and well engineered. Punching above its star count.

Private Inference Network on Idle Macs

Go213 starsOtherupdated today

Outstanding work. A score of 96/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
86
EngineeringTests, CI, linting, lockfiles
100
Project healthDescription, activity, stars, deps
100

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  2. 2
    CI/CD
    EngineeringInfo

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  3. 3
    README
    DocumentationIssue

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

Detailed breakdown

Documentation

86
  • README70
    • README is present.
    • README is well structured with multiple sections.
    • No screenshots or images in the README (−20 pts).Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    • README has code examples.
    • README links to a live demo or deployed app.
    • No status badges in the README (−10 pts).Add CI/build status badges from shields.io or your CI provider to signal project health.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • No .env.example found (−10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under Other.
  • Contributing guide100
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide describes code style expectations.
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

100
  • Tests100
    • Test files detected (admin-ui/src/lib/format.test.ts).
    • Go module github.com/eigeninference/d-inference has test files. Run with `go test ./...`.
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/ci.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI caches dependencies for faster runs.
    • CI includes a build step.
  • Linting and formatting100
    • Formatting enforced (.golangci.yml).
  • Reproducibility100
    • Lockfile present (go.sum). Installs are reproducible.
    • Environment pinned via coordinator/Dockerfile.
    • Dependabot covers 2 ecosystems (gomod, npm). Dependencies stay current.
    • Dependabot is not configured for GitHub Actions.Add a `package-ecosystem: github-actions` entry to keep workflow action versions up to date.
    • go.mod pins Go version 1.25.0.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Project health

100
  • Dependency manifest100
    • Dependency manifest found (go.mod).
    • go.mod module path is fully qualified (github.com/eigeninference/d-inference).
    • go.mod specifies Go version 1.25.0.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: Go.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 213 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 42
    Forks
  • 130
    Releaseslatest 2mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 213
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 9h
    Median PR merge time
  • 152
    Open issues
Repository files27 root entries
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (gomod, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • admin-ui
    Good: Test files detected (admin-ui/src/lib/format.test.ts).
  • console-ui
  • coordinator
    Good: Environment pinned via coordinator/Dockerfile.
  • deploy
  • docs
  • e2e
  • landing
  • libs
  • papers
  • provider-swift
  • scripts
  • .gcloudignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .golangci.yml
    Good: Formatting enforced (.golangci.yml).
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • mise.toml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.