mrnerf/lichtfeld-studio
Grade a repo

77

/ 100

GradeB

Well engineered. The main gap is linting.

Top 16% of 5,156 graded repos

Train, inspect, edit, automate, and export 3D Gaussian Splatting scenes from a single native application.

Documentation96
Engineering77
Health100
C++3,977GPL-3.03d ago

Top fixes

Highest-impact changes first, ranked by point weight

8 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
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  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

96

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

77

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.

Tests18pt80

Test files detected (external/OpenMesh/cmake-library/CI/tests).

CI/CD14pt85

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

Reproducibility6pt92

Lockfile present (docs/pnpm-lock.yaml). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/package.json).

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

  • 228 / 1597
    Commits (30d / 90d)
  • 514
    Forks
  • 16
    Releaseslatest 2mo ago

Community

  • 57% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 3,977
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 2h
    Median PR merge time
  • 239
    Open issues
Repository files30 root entries
  • .github
    Good: CI is configured (.github/workflows/windows-build-preflight.yml).
    Good: Dependabot configured for vcpkg.
    Good: Issue or PR templates present.
  • .vscode
  • cmake
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • docs
    Good: Lockfile present (docs/pnpm-lock.yaml). Installs are reproducible.
    Good: Dependency manifest found (docs/package.json).
  • eval
  • external
    Good: Test files detected (external/OpenMesh/cmake-library/CI/tests).
  • resources
  • scripts
  • src
  • tests
  • tools
  • .clang-format
  • .clang-tidy
  • .clangd
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mcp.json
  • AGENTS.md
  • build_lichtfeld.ps1
  • CMakeLists.txt
  • CMakePresets.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under GPL-3.0.
  • LICENSE-EXCEPTION.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.
  • THIRD_PARTY_LICENSES.md
  • vcpkg-configuration.json
  • vcpkg.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/mrnerf/lichtfeld-studio)](https://www.repo-grade.com/report/mrnerf/lichtfeld-studio)

More graded C++ repos