xuzhougeng/wispterm
Grade a repo

80

/ 100

GradeB

Well engineered. The main gaps are linting and a contributing guide.

Top 20% of 5,156 graded repos

A cross-platform terminal workspace for remote development and AI agent workflows, powered by libghostty-vt

Documentation95
Engineering76
Health100
Zig445MIT28d ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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 lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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 guide5pt66

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

76

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.

Tests18pt80

Test files detected (docs/test).

Reproducibility6pt80

Lockfile present (remote/package-lock.json). Installs are reproducible.

CI/CD14pt85

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/package.json).

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

  • 32 / 116
    Commits (30d / 90d)
  • 28
    Forks
  • 130
    Releaseslatest 6mo ago

Community

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

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • assets
  • debug
  • docs
    Good: Test files detected (docs/test).
    Good: Dependency manifest found (docs/package.json).
  • packaging
  • pkg
  • plans
  • plugins
  • release-notes
  • remote
    Good: Lockfile present (remote/package-lock.json). Installs are reproducible.
    Good: Environment pinned via remote/Dockerfile.
  • shaders
  • src
  • tests
  • tools
  • vendor
  • wiki
  • .gitignore
    Good: .gitignore present.
  • .zenodo.json
  • AGENTS.md
  • build.zig
  • build.zig.zon
  • CITATION.cff
  • 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.
    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.
    Good: Contributing guide includes code examples.
  • KNOWN_ISSUES.md
  • LICENSE
    Good: Licensed under MIT.
  • LINUX_SHORTCUT_TEST_PLAN.md
  • Makefile
  • pytest.ini
  • 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.
  • README.zh-CN.md
  • ROADMAP.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/xuzhougeng/wispterm)](https://www.repo-grade.com/report/xuzhougeng/wispterm)

More graded Zig repos