Industry-defining adoption. A few engineering gaps, but the community carries it.

Godot Engine – Multi-platform 2D and 3D game engine

Documentation

62

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

80

CI/CD14pt68

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

Reproducibility6pt70

Lockfile present (platform/web/package-lock.json). Installs are reproducible.

Tests18pt80

Test files detected (modules/csg/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/android_builds.yml).
    Good: Issue or PR templates present.
  • core
  • doc
  • drivers
  • editor
  • main
  • misc
  • modules
    Good: Test files detected (modules/csg/tests).
  • platform
    Good: Lockfile present (platform/web/package-lock.json). Installs are reproducible.
  • scene
  • servers
  • tests
  • thirdparty
  • .clang-format
  • .clang-tidy
  • .clangd
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .pre-commit-config.yaml
  • AUTHORS.md
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • COPYRIGHT.txt
  • DONORS.md
  • gles3_builders.py
  • glsl_builders.py
  • LICENSE.txt
    Good: Licensed under MIT.
  • methods.py
  • platform_methods.py
  • pyproject.toml
    Good: Dependency manifest found (pyproject.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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SConstruct
  • scu_builders.py
  • version.py