govtechsg/sgds-web-component
Grade a repo

0

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 7% of 5,156 graded repos

SGDS Web component written in Lit 3

Documentation99
Engineering93
Health86
TypeScript18MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

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

99

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt85

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

Tests18pt100

Test files detected (scripts/__tests__).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt75

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 7
    Forks
  • 67
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 18d 23h
    Median issue response
  • 5d 17h
    Median PR merge time
  • 71
    Open issues
Repository files51 root entries
  • .claude
  • .github
    Good: Licensed under MIT.
    Good: CI is configured (.github/workflows/a11y.yml).
    Good: Issue or PR templates present.
  • .husky
  • .storybook
  • .vscode
  • contributing
  • coverage
  • cypress
    Good: Environment pinned via cypress/apps/next-app/Dockerfile.
  • docs
  • mocks
  • playground
  • plop-templates
  • scripts
    Good: Test files detected (scripts/__tests__).
  • skills
  • src
    Issue: Build artifacts or local files may be committed (src/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • stories
  • test
  • typings
  • .babelrc
  • .env.sample
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • .prettierignore
  • amplify.yml
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_CONVENTIONS.md
  • commitlint.config.js
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • custom-elements-manifest.config.mjs
  • cypress.config.ts
  • GITHUB_SNIPPETS_AUDIT.md
  • gulpfile.babel.js
  • index.html
  • LICENSE
  • package.json
    Good: Dependency manifest found (package.json).
  • plopfile.mjs
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm.workspace.yaml
  • prettier.config.js
  • 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.
  • rollup.config.mjs
  • rollup.test.config.js
  • sgds-design-alpha-testing.zip
  • tailwind.config.js
  • tsconfig.json
  • tsconfig.test.json
  • validation.html
  • vite.config.mjs
  • web-test-runner.config.mjs
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/govtechsg/sgds-web-component)](https://www.repo-grade.com/report/govtechsg/sgds-web-component)

More graded TypeScript repos