82
/ 100
Good shape overall. A few tweaks would push it into the top tier.
SQL Tools API service that provides SQL Server data management capabilities.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
76
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
79
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
Test files detected (test).
CI is configured (.github/workflows/integration-tests.yml).
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (sqltoolsservice.sln).
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)
- 166Forks
- 1000Releaseslatest 8y ago
Community
- 75% - GoodCommunity health
- -authors own >50% of commits
- 504Watchers
Responsiveness
- 11hMedian issue response
- 11hMedian PR merge time
- 70Open issues
Repository files34 root entries
- .config
- .githubGood: CI is configured (.github/workflows/integration-tests.yml).Good: Dependabot covers 2 ecosystems (github-actions, dotnet-sdk). Dependencies stay current.Good: Issue or PR templates present.
- .vscode
- azure-pipelines
- bin
- docs
- localization
- packages
- scripts
- src
- testGood: Test files detected (test).
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mention-bot
- build.cake
- build.cmd
- build.json
- BUILD.md
- build.ps1
- build.sh
- codecov.yml
- Directory.Build.props
- Directory.Build.targets
- global.json
- license.txtGood: Licensed under Other.
- Notice.txt
- nuget.config
- Packages.props
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README documents how to install the project.Good: README documents how to run the project.
- RefreshDllsForTestRun.cmd
- SECURITY.mdGood: Security policy present.
- SQL2003.snk
- sqltoolsservice.slnGood: Dependency manifest found (sqltoolsservice.sln).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/microsoft/sqltoolsservice)