ilysenko/codex-desktop-linux
Grade a repo

87

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 18% of 5,156 graded repos

Run OpenAI Codex Desktop on Linux - automated installer

Documentation83
Engineering85
Health100
JavaScript1,987MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

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

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated 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

83

README12pt70

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

85

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.

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (record-replay-linux/tests).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Rust linting configured (cargo clippy in CI, cargo fmt in CI).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

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

  • 185 / 750
    Commits (30d / 90d)
  • 255
    Forks
  • 0
    Releases

Community

  • 57% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 1,987
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 1d 15h
    Median PR merge time
  • 6
    Open issues
Repository files29 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • assets
  • computer-use-linux
  • contrib
  • docs
  • launcher
  • linux-features
  • nix
  • packaging
  • plugins
  • read-aloud-linux
  • record-replay-linux
    Good: Test files detected (record-replay-linux/tests).
  • scripts
  • tests
  • updater
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • config.toml
  • 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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • flake.lock
  • flake.nix
  • install.sh
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    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/ilysenko/codex-desktop-linux)](https://www.repo-grade.com/report/ilysenko/codex-desktop-linux)

More graded JavaScript repos