modality-org/modality
Grade a repo

0

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 33% of 5,156 graded repos

verifiable contracts using temporal modal logic

Documentation73
Engineering78
Health94
Rust18MIT1mo 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

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

  3. 3
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  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

73

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

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

README12pt90

README is present.

License6pt100

Licensed under MIT.

Engineering

78

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.

Tests18pt80

Test files detected (js/jest.config.js).

Reproducibility6pt80

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

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (js/.eslintrc.json).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (common/modality-vscode/package.json).

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

  • -
    Commits (30d / 90d)
  • 1
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 11d 9h
    Median issue response
  • 1h
    Median PR merge time
  • 0
    Open issues
Repository files30 root entries
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build-packages.yml).
  • .vscode
  • common
    Good: Dependency manifest found (common/modality-vscode/package.json).
  • content
  • dev
  • docs
  • examples
  • experiments
    Good: Security policy present.
    Issue: Build artifacts or local files may be committed (experiments/llm-synthesizer/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
  • fixtures
  • grammars
  • js
    Good: Test files detected (js/jest.config.js).
    Good: Linter or formatter configured (js/.eslintrc.json).
    Good: Environment pinned via js/.node-version.
  • packages
  • papers
  • rust
  • scripts
  • services
  • sites
  • skills
  • tests
  • tutorials
  • .gitignore
    Good: .gitignore present.
  • content-calendar-q1-2026.md
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEVELOPMENT.md
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • ROADMAP-AGENT-COOPERATION.md
  • shoal-consensus-implementation.plan.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/modality-org/modality)](https://www.repo-grade.com/report/modality-org/modality)

More graded Rust repos