synthstromaudible/delugefirmware

0

/ 100

Documentation63
Engineering83
Health100
C++660GPL-3.01d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Firmware for the Synthstrom Audible Deluge

Documentation

63

Install and run instructions9pt45

README documents how to install the project.

README12pt55

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under GPL-3.0.

Engineering

83

CI/CD14pt72

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

Tests18pt80

Test files detected (tests).

Reproducibility6pt90

Lockfile present (scripts/toolchain/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (scripts/toolchain/requirements.txt).

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

  • —
    Commits (30d / 90d)
  • 156
    Forks
  • 7
    Releaseslatest 2d ago

Community

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

Responsiveness

  • 17h
    Median issue response
  • 14h
    Median PR merge time
  • 110
    Open issues
Repository files30 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 3 ecosystems (github-actions, pip, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • assets
  • contrib
  • docs
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
    Good: Code of conduct present.
  • IDE_Configs
  • lib
  • scripts
    Good: Lockfile present (scripts/toolchain/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (scripts/toolchain/requirements.txt).
  • src
  • tests
    Good: Test files detected (tests).
  • toolchain
  • website
  • .clang-format
  • .clang-format-ignore
  • .clang-tidy
  • .clangd
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • CHANGELOG.md
  • CMakeLists.txt
  • CODEOWNERS
  • dbt
  • dbt.cmd
  • dbt.py
  • LICENSE
    Good: Licensed under GPL-3.0.
  • linker_script_rz_a1l.ld
  • Makefile
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.