94
/ 100
Excellent work. The main thing left to polish is dependency metadata.
SGDS Web component written in Lit 3
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, 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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
99
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
93
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/pr-tests.yml).
Test files detected (scripts/__tests__).
Linter or formatter configured (.eslintrc.json).
Issue or PR templates present.
Project health
86
.gitignore present.
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 55 / 196Commits (30d / 90d)
- 11Forks
- 76Releaseslatest 2y ago
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 17Watchers
Responsiveness
- 18d 23hMedian issue response
- 5d 17hMedian PR merge time
- 82Open issues
Repository files51 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/pr-tests.yml).Good: Issue or PR templates present.
- .husky
- .storybook
- .vscode
- contributing
- cypressGood: Environment pinned via cypress/apps/next-app/Dockerfile.
- docs
- mocks
- playground
- plop-templates
- scriptsGood: Test files detected (scripts/__tests__).
- skills
- srcIssue: 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.jsonGood: Linter or formatter configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .nvmrc
- .prettierignore
- amplify.yml
- CHANGELOG.md
- CLAUDE.md
- CODE_CONVENTIONS.md
- commitlint.config.js
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- plopfile.mjs
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm.workspace.yaml
- prettier.config.js
- README.mdGood: 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.
- rolldown.config.mjs
- rolldown.test.config.mjs
- sgds-design-alpha-testing.zip
- tailwind.config.js
- tsconfig.json
- tsconfig.test.json
- validation.html
- vite.config.mjs
- vitest.config.ts
- web-test-runner.config.mjs
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/govtechsg/sgds-web-component)