tuna-os/tunaos
Grade a repo

0

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Top 47% of 5,156 graded repos

Bringing a modern cloud-native experience to the Enterprise Linux Desktop

Documentation95
Engineering53
Health68
Shell47Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).

See your top fixes
Now
D
69
Potential
B
82

Top fixes

Highest-impact changes first, ranked by point weight

15 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 `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

95

Contributing guide5pt83

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

53

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/CD14pt40

CI is configured (.github/workflows/build-albacore.yml).

Tests18pt80

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

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)
  • 2
    Forks
  • 42
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • 12d 2h
    Median issue response
  • <1h
    Median PR merge time
  • 36
    Open issues
Repository files52 root entries
  • _upstream-snapshots
  • .flatpak-builder
  • .github
    Good: CI is configured (.github/workflows/build-albacore.yml).
    Good: Issue or PR templates present.
  • .pi
  • blog
  • build_scripts
  • docs
  • iso_files
  • live-iso
  • rfcs
  • scripts
  • system_files
  • system_files_overrides
  • tests
    Good: Test files detected (tests).
  • .devcontainer.json
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pre-commit-config.yaml
  • .yamllint.yml
  • ADOPTERS.md
  • AGENTS.md
  • artifacthub-repo.yml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • COMMUNITY.md
  • config.toml
  • Containerfile
  • Containerfile.final
  • Containerfile.hwe
  • Containerfile.nvidia
  • Containerfile.ubuntu
  • context.md
  • CONTEXT.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    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.
  • cosign.pub
  • handoff.md
  • image-versions.yaml
  • image.toml
  • Justfile
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS.md
  • MIGRATION.md
  • plan.md
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • registry-map.yaml
  • renovate.json
  • research.md
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.
  • tuna.txt
  • ubuntu.txt
  • VERSIONING.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/tuna-os/tunaos)](https://www.repo-grade.com/report/tuna-os/tunaos)

More graded Shell repos