microsoft/sqltoolsservice

0

/ 100

Documentation76
Engineering79
Health100
C#504Other1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

SQL Tools API service that provides SQL Server data management capabilities.

Documentation

76

Contributing guide5pt25

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

79

Reproducibility6pt20

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

Tests18pt80

Test files detected (test).

CI/CD14pt85

CI is configured (.github/workflows/integration-tests.yml).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (sqltoolsservice.sln).

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)
  • 166
    Forks
  • 1000
    Releaseslatest 7y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 504
    Watchers

Responsiveness

  • 11h
    Median issue response
  • 11h
    Median PR merge time
  • 73
    Open issues
Repository files34 root entries
  • .config
  • .github
    Good: 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
  • test
    Good: Test files detected (test).
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .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.txt
    Good: Licensed under Other.
  • Notice.txt
  • nuget.config
  • Packages.props
  • README.md
    Good: 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.md
    Good: Security policy present.
  • SQL2003.snk
  • sqltoolsservice.sln
    Good: Dependency manifest found (sqltoolsservice.sln).