sashiko-dev/sashiko
Grade a repo

81

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and linting.

Top 24% of 5,156 graded repos

Agentic review of Linux Kernel code changes

Documentation94
Engineering70
Health100
Rust1,327Apache-2.028d ago

Top fixes

Highest-impact changes first, ranked by point weight

8 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
    Install and run instructions9pt

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

  3. 3
    Issue and PR templates6pt

    Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

  4. 4
    Issue and PR templates6pt

    A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

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.

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 (tests).

CI/CD14pt100

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

Reproducibility6pt100

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

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

  • 242 / 729
    Commits (30d / 90d)
  • 243
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 7h
    Median issue response
  • 1h
    Median PR merge time
  • 87
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
  • benchmarks
  • deployment
  • designs
  • docs
  • projects
  • scripts
  • src
  • static
  • tests
    Good: Test files detected (tests).
  • third_party
  • .dockerignore
  • .gcloudignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .yamllint
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • flake.lock
  • flake.nix
  • GEMINI.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS_GUIDE.md
  • Makefile
  • PRESS.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.
  • rust-toolchain.toml
  • Settings.toml
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/sashiko-dev/sashiko)](https://www.repo-grade.com/report/sashiko-dev/sashiko)

More graded Rust repos