qualcomm-linux/meta-qcom

0

/ 100

Documentation85
Engineering16
Health68
BitBake135MIT1d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

OpenEmbedded/Yocto Project BSP layer for Qualcomm based platforms

Documentation

85

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

16

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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/build-yocto.yml).

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 292
    Forks
  • 1
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • 7h
    Median issue response
  • 24h
    Median PR merge time
  • 231
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/build-yocto.yml).
  • ci
  • classes
  • classes-recipe
  • conf
  • docs
  • dynamic-layers
  • lib
  • licenses
    Good: Licensed under MIT.
  • patches
  • recipes-bsp
  • recipes-connectivity
  • recipes-core
  • recipes-devtools
  • recipes-graphics
  • recipes-kernel
  • recipes-ml
  • recipes-multimedia
  • recipes-support
  • recipes-test
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • COPYING.MIT
  • README
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.md
  • SECURITY.md
    Good: Security policy present.