qualcomm/eld
Grade a repo

0

/ 100

GradeC

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

Top 39% of 5,156 graded repos

Embedded Linker (eld)

Documentation89
Engineering56
Health100
C++244BSD-3-Clause1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under BSD-3-Clause.

Engineering

56

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-win.yml).

Tests18pt80

Test files detected (etc/vim/test).

Reproducibility6pt82

Lockfile present (docs/userguide/requirements.txt). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/userguide/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)
  • 65
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 244
    Watchers

Responsiveness

  • 11h
    Median issue response
  • 8h
    Median PR merge time
  • 223
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/ci-win.yml).
    Good: Dependabot configured for github-actions.
  • cmake
  • docs
    Good: Lockfile present (docs/userguide/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (docs/userguide/requirements.txt).
  • etc
    Good: Test files detected (etc/vim/test).
  • include
  • lib
  • Plugins
  • presentations
  • templates
  • test
  • tools
  • utils
  • .clang-format
  • .clang-tidy
  • .gitignore
    Good: .gitignore present.
  • .licenseignore
  • About.md
  • CHANGELOG.md
  • CMakeLists.txt
  • CODE-OF-CONDUCT.md
  • CODEOWNERS
  • configure_external_llvm.sh
  • CONTRIBUTING.md
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • README.md
    Good: 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.
  • repolint.json
  • ROADMAP.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/qualcomm/eld)](https://www.repo-grade.com/report/qualcomm/eld)

More graded C++ repos