0
/ 100
Polished and well engineered. Punching above its star count.
[Experimental] A fast, friendly linter for JavaScript, TypeScript, and more. ❤️🔥
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add more sections (Overview, Install, Usage, Contributing) using ## headings.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a section showing how to install dependencies.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
73
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
CONTRIBUTING guide found.
README is present.
Licensed under MIT.
Engineering
98
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (packages/astro-language/src/astroCompilerDiagnosticToLanguageReport.test.ts).
CI is configured (.github/workflows/ci.yaml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
97
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 28Forks
- 13Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 293Watchers
Responsiveness
- 24d 1hMedian issue response
- <1hMedian PR merge time
- 375Open issues
Repository files33 root entries
- .agents
- .changeset
- .githubGood: 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: Code of conduct present.Good: CI is configured (.github/workflows/ci.yaml).Good: Issue or PR templates present.Good: Security policy present.
- .helix
- .husky
- .vscode
- @types
- docs
- packagesGood: Test files detected (packages/astro-language/src/astroCompilerDiagnosticToLanguageReport.test.ts).
- scripts
- .all-contributorsrc
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- AGENTS.md
- cspell.json
- eslint.config.ts
- flint.config.ts
- knip.ts
- LICENSE.mdGood: Licensed under MIT.
- lint-staged.config.js
- netlify.toml
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- prettier.config.ts
- README.mdGood: README is present.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.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- tsconfig.base.json
- tsconfig.json
- tsdown.config.ts
- vitest.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/flint-fyi/flint)