aros-development-team/aros
Grade a repo

76

/ 100

GradeC

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

Top 38% of 5,156 graded repos

Main AROS repository for active development. Contains the main Operating System components and Build System.

Documentation74
Engineering70
Health94
C480Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 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
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  3. 3
    Install and run instructions9pt

    Add a section showing how to install dependencies.

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

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

74

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under Other.

Engineering

70

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.

Tests18pt80

Test files detected (arch/all-pc/udis86/tests).

CI/CD14pt100

CI is configured (external/openurl/.travis.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (arch/all-pc/udis86/BuildVS2010/udis86.sln).

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

  • 44 / 221
    Commits (30d / 90d)
  • 82
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 480
    Watchers

Responsiveness

  • 5d 24h
    Median issue response
  • 2h
    Median PR merge time
  • 97
    Open issues
Repository files34 root entries
  • .github
    Good: Issue or PR templates present.
  • arch
    Good: Test files detected (arch/all-pc/udis86/tests).
    Good: Dependency manifest found (arch/all-pc/udis86/BuildVS2010/udis86.sln).
  • boot
  • bootstrap
  • compiler
  • config
  • developer
  • external
    Good: CI is configured (external/openurl/.travis.yml).
  • images
    Issue: Build artifacts or local files may be committed (images/IconSets/Gorilla/Icons/Small/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • rom
  • scripts
  • tools
  • workbench
  • .astyle
  • .codacy.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • acinclude.m4
  • ACKNOWLEDGEMENTS
  • aclocal.m4
  • configure
  • configure.in
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LEGAL
  • LICENSE
    Good: Licensed under Other.
  • LICENSE.Author
  • LICENSE.GPL
  • license.html
  • LICENSE.LGPL
  • Makefile.in
  • mmake.config.in
  • mmakefile
  • 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.
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/aros-development-team/aros)](https://www.repo-grade.com/report/aros-development-team/aros)

More graded C repos