0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
High-performance GPU-accelerated signal processing and visualization framework that runs anywhere.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
87
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
55
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.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/ci.yml).
Test files detected (tests).
Lockfile present (packages/docs-content/bun.lock). Installs are reproducible.
Project health
100
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 44Forks
- 15Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 739Watchers
Responsiveness
- 4hMedian issue response
- 8d 6hMedian PR merge time
- 16Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- apps
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.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.
- examples
- include
- meson
- packagesGood: Lockfile present (packages/docs-content/bun.lock). Installs are reproducible.
- python
- resources
- src
- subprojects
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under MIT.
- main.cc
- meson_options.txt
- meson.build
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/luigifcruz/cyberether)