luigifcruz/cyberether

0

/ 100

Documentation87
Engineering55
Health100
C++739MIT1d ago
Grade a repo

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.

Documentation

87

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt95

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

55

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.

Issue and PR templates6pt0

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/CD14pt57

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

Tests18pt80

Test files detected (tests).

Reproducibility6pt80

Lockfile present (packages/docs-content/bun.lock). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

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)
  • 44
    Forks
  • 15
    Releaseslatest 2mo ago

Community

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

Responsiveness

  • 4h
    Median issue response
  • 8d 6h
    Median PR merge time
  • 16
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • apps
  • docs
    Good: 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
  • packages
    Good: Lockfile present (packages/docs-content/bun.lock). Installs are reproducible.
  • python
  • resources
  • src
  • subprojects
  • tests
    Good: Test files detected (tests).
  • .gitignore
    Good: .gitignore present.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
    Good: Licensed under MIT.
  • main.cc
  • meson_options.txt
  • meson.build
  • 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.
    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.