0
/ 100
Popular and well-maintained. A little polish away from elite status.
Dapper - a simple object mapper for .Net
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
63
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Other.
Engineering
77
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
Test files detected (benchmarks/Dapper.Tests.Performance/LegacyTests.cs).
CI is configured (.github/workflows/main.yml).
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (Build.csproj).
Repository has a description.
.gitignore present.
Repository files33 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Issue or PR templates present.
- benchmarksGood: Test files detected (benchmarks/Dapper.Tests.Performance/LegacyTests.cs).
- Dapper
- Dapper.EntityFramework
- Dapper.EntityFramework.StrongName
- Dapper.ProviderTools
- Dapper.Rainbow
- Dapper.SqlBuilder
- Dapper.StrongName
- docs
- signatures
- testsGood: Environment pinned via tests/docker-compose.yml.
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- appveyor.yml
- build.cmd
- Build.csprojGood: Dependency manifest found (Build.csproj).
- build.ps1
- Dapper.png
- Dapper.sln.DotSettings
- Dapper.sln.old
- Dapper.slnx
- Dapper.snk
- Directory.Build.props
- Directory.Build.targets
- Directory.Packages.props
- global.json
- License.txtGood: Licensed under Other.
- NonCLA.md
- nuget.config
- Readme.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.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.
- version.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dapperlib/dapper)