gabrielatwell1987/portfolio
Grade a repo

0

/ 100

GradeF

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

Higher than 37% of 5,156 graded repos

Portfolio of Gabriel Atwell

Documentation25
Engineering56
Health89
Svelte91mo 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 C (79).

See your top fixes
Now
F
52
Potential
C
79

Top fixes

Highest-impact changes first, ranked by point weight

18 to address
  1. 1
    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.

  2. 2
    README12pt

    Expand with a description, install steps, usage, and examples.

  3. 3
    README12pt

    Add more sections (Overview, Install, Usage, Contributing) using ## headings.

  4. 4
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

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

25

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

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.

Install and run instructions9pt10

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

→ Add a section showing how to install dependencies.

README12pt58

README is present.

Engineering

56

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.

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.

Reproducibility6pt70

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (src/lib/components/tests).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.cjs).

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

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

  • 28% - Weak
    Community health
  • -
    authors own >50% of commits
  • 9
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files26 root entries
  • .fallow
  • .husky
  • docs
  • src
    Good: Test files detected (src/lib/components/tests).
  • static
  • .env.example
  • .eslintignore
  • .eslintrc.cjs
    Good: Linter or formatter configured (.eslintrc.cjs).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.json
  • .npmrc
  • .oxfmtrc.json
  • .oxlintrc.json
  • .prettierrc
  • CHANGELOG.md
  • markdownlint.json
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • skills-lock.json
  • svelte.config.js
  • tsconfig.json
  • vite.config.js
  • vitest-setup.ts
  • wrangler.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/gabrielatwell1987/portfolio)](https://www.repo-grade.com/report/gabrielatwell1987/portfolio)

More graded Svelte repos