riscv/riscv-arch-test
Grade a repo

88

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 16% of 5,156 graded repos

The RISC-V Architectural Certification Tests (ACTs) are a set of assembly language tests designed to certify that a design faithfully implements the RISC-V specification.

Documentation85
Engineering86
Health100
Assembly743Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 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

85

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

86

Tests18pt80

Test files detected (generators/testgen/src/testgen/data/test_chunk.py).

Reproducibility6pt80

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

CI/CD14pt85

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.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

  • 92 / 402
    Commits (30d / 90d)
  • 330
    Forks
  • 216
    Releaseslatest 4y ago

Community

  • 62% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 743
    Watchers

Responsiveness

  • 22h
    Median issue response
  • 3d 24h
    Median PR merge time
  • 100
    Open issues
Repository files29 root entries
  • .github
    Good: CI is configured (.github/workflows/build-image.yml).
    Good: Issue or PR templates present.
  • config
  • coverpoints
  • docs
  • framework
  • generators
    Good: Test files detected (generators/testgen/src/testgen/data/test_chunk.py).
  • testplans
  • tests
  • tests-dev
  • .codespellrc
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mise.toml
  • .pre-commit-config.yaml
  • .python-version
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    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.
  • COPYING.APACHE
  • COPYING.BSD
  • COPYING.CC
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Makefile
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
  • renovate.json
  • run_tests.py
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
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/riscv/riscv-arch-test)](https://www.repo-grade.com/report/riscv/riscv-arch-test)

More graded Assembly repos