alialib/alia

0

/ 100

Documentation59
Engineering46
Health68
C++118MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

a declarative UI library for C/C++

Documentation

59

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt78

README is present.

License6pt100

Licensed under MIT.

Engineering

46

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

Tests18pt80

Test files detected (legacy/tests).

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)
  • 6
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 11d 1h
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/clang.yml).
  • apis
  • assets
  • benchmarks
  • cmake
  • core
  • drivers
  • examples
  • legacy
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (legacy/tests).
  • scripts
  • tests
  • tools
  • .clang-format
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CMakeLists.txt
  • codecov.yml
  • LICENSE.txt
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • vcpkg.json