0

/ 100

GradeF

Getting noticed, but rough fundamentals could turn visitors away.

Higher than 13% of 5,156 graded repos

Is Parallel Programming Hard, And If So, What Can You Do About It?

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to D (64).

See your top fixes
Now
F
20
Potential
D
64

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  2. 2
    CI/CD14pt

    If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

  3. 3
    README12pt

    Add a README.md describing what the project does, how to install it, and how to run it.

  4. 4
    Install and run instructions9pt

    Add a section showing how to install dependencies.

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

19

README12pt0

No README found in the repository.

→ Add a README.md describing what the project does, how to install it, and how to run it.

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

License6pt100

Licensed under Other.

Engineering

1

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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

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

Community

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

Responsiveness

  • 1d 2h
    Median issue response
  • 1d 6h
    Median PR merge time
  • 2
    Open issues
Repository files51 root entries
  • .Templates
  • advsync
  • appendix
  • bib
  • cartoons
  • CodeSamples
  • count
  • cpu
  • datastruct
  • debugging
  • defer
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • easy
  • fonts
  • formal
  • future
  • howto
  • intro
  • locking
  • memalloc
  • memorder
  • owned
  • SMPdesign
  • together
  • toolsoftrade
  • utilities
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • a2ping-rule.mk
  • ack.tex
  • alphapf.bst
  • COPYING
  • epstopdf-rule.mk
  • FAQ-BUILD.txt
  • FAQ.txt
  • fixfvextra.ltx
  • glossary.tex
  • glsdict.tex
  • indexsee.tex
  • legal.tex
  • Makefile
  • Makefile.2022.01.25
  • origpub.sty
  • pagegroup
  • perfbook-lt.tex
  • pfbook.cls
  • pfhyphex.tex
  • qqz.sty
  • summary.tex
  • todo.txt
  • ushyphex.tex
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/paulmckrcu/perfbook)](https://www.repo-grade.com/report/paulmckrcu/perfbook)

More graded TeX repos