Popular for its size, but the engineering basics lag behind the interest.

Free Open Motorsports ECU

Documentation

54

Install and run instructions9pt0

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

Add a section showing how to install dependencies.

README12pt65

README is present.

Contributing guide5pt69

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.

License6pt100

Licensed under Other.

Engineering

67

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.

Reproducibility6pt12

No dependency lockfile found (−70 pts).

Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Tests18pt80

Test files detected (java_console/autotest/src/main/java/com/rusefi/common/MiscTest.java).

CI/CD14pt85

CI is configured (.github/workflows/build-firmware.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (java_console/autotest/build.gradle).

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

  • Commits (30d / 90d)
  • 60
    Forks
  • 10
    Releaseslatest 20d ago

Community

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

Responsiveness

  • 51d 13h
    Median issue response
  • 8h
    Median PR merge time
  • 223
    Open issues
Repository files19 root entries
  • .claude
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/build-firmware.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .vscode
  • firmware
  • java_console
    Good: Test files detected (java_console/autotest/src/main/java/com/rusefi/common/MiscTest.java).
    Good: Dependency manifest found (java_console/autotest/build.gradle).
    Issue: Build artifacts or local files may be committed (java_console/.idea/.name) (−40 pts).Fix: Remove them and add to .gitignore.
  • java_tools
  • misc
  • simulator
  • unit_tests
  • .clang-format
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CLAUDE.md
  • 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.
    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.
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • format.sh
  • LICENSE
    Good: Licensed under Other.
  • 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.
    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.