0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
TUI framework and developer productivity apps in Rust 🦀
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
89
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
68
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (tui/src/core/ansi/vt_100_pty_output_parser/vt_100_pty_output_conformance_tests/tests).
Rust linting configured (rustfmt.toml).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 32Forks
- 19Releaseslatest 12mo ago
Community
- -Community health
- -authors own >50% of commits
- 475Watchers
Responsiveness
- 5d 8hMedian issue response
- 2hMedian PR merge time
- 65Open issues
Repository files52 root entries
- .agents
- .cargo
- .gemini
- .githubGood: Issue or PR templates present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
- .vscode
- analytics_schema
- build-infra
- cmdr
- docs
- task
- tuiGood: Test files detected (tui/src/core/ansi/vt_100_pty_output_parser/vt_100_pty_output_conformance_tests/tests).
- vendored-crates
- .gitconfig
- .gitignoreGood: .gitignore present.
- .prettierignore
- 1.code-search
- 2.code-search
- AGENTS.md
- bacon.toml
- bootstrap.sh
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- check_cargo.fish
- check_cli.fish
- check_constants.fish
- check_detection.fish
- check_docs.fish
- check_lock.fish
- check_orchestrators.fish
- check_recovery.fish
- check_toolchain.fish
- check_watch.fish
- check.fish
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: 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.
- deny.toml
- GEMINI.md
- LICENSEGood: Licensed under Apache-2.0.
- lychee.toml
- r3bl-term.svg
- README.mdGood: 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.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.
- remove_toolchains.sh
- run.fish
- rust-toolchain-sync-to-toml.fish
- rust-toolchain-update.fish
- rust-toolchain-validate.fish
- rust-toolchain.toml
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml).
- script_lib.fish
- tmux-r3bl-dev.fish
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/r3bl-org/r3bl-open-core)