riscv/meta-riscv

0

/ 100

Documentation67
Engineering29
Health59
BitBake438Other1d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

OpenEmbedded/Yocto layer for RISC-V Architecture

Documentation

67

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 instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt85

README is present.

License6pt100

Licensed under Other.

Engineering

29

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.

CI/CD14pt57

CI is configured (.github/workflows/check-layer.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

59

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.

Housekeeping3pt40

No .gitignore found (−60 pts).

→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 177
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 5h
    Median issue response
  • 5h
    Median PR merge time
  • 25
    Open issues
Repository files23 root entries
  • .github
    Good: CI is configured (.github/workflows/check-layer.yml).
    Good: Issue or PR templates present.
  • bitbake-registry
  • classes
  • conf
  • docs
  • dynamic-layers
  • files
  • kas
  • licenses
  • recipes-bsp
  • recipes-core
  • recipes-devtools
  • recipes-graphics
  • recipes-kernel
  • recipes-multimedia
  • recipes-support
  • tools
  • .travis.yml
  • CONTRIBUTORS
  • DEPRECATED.md
  • LICENSE
    Good: Licensed under Other.
  • 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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.