strappazzon/www
Grade a repo

0

/ 100

GradeD

Early stage. Tests, CI, and a strong README would raise this score quickly.

Higher than 48% of 5,156 graded repos

🌐 My website

Documentation68
Engineering53
Health86
SCSS5MIT2mo ago

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 A (90).

See your top fixes
Now
D
64
Potential
A
90

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    Tests18pt

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

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  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

68

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt68

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

Licensed under MIT.

Engineering

53

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt72

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

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (Gemfile).

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)
  • 0
    Forks
  • 0
    Releases

Community

  • 100% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 5
    Watchers

Responsiveness

  • -
    Median issue response
  • 17d 22h
    Median PR merge time
  • 0
    Open issues
Repository files31 root entries
  • _components
  • _data
  • _plugins
  • _root
  • _sass
  • _templates
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: CI is configured (.github/workflows/build-dev.yml).
    Good: Issue or PR templates present.
  • .vscode
  • bin
  • pages
  • static
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .jekyll.yml
  • .markdownlint.yml
  • .rubocop.yml
  • .stylelintignore
  • .stylelintrc.yml
  • .tool-versions
    Good: Environment pinned via .tool-versions.
  • eslint.config.mjs
  • frontmatter.json
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE-CODE.txt
  • LICENSE-CONTENT.txt
  • package-lock.json
  • package.json
  • projects
  • SUPPORT.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/strappazzon/www)](https://www.repo-grade.com/report/strappazzon/www)

More graded SCSS repos