A top-tier open source project. Docs, tests, and CI are all in excellent shape.

EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.

Documentation

86

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

80

Reproducibility6pt30

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (benchmark/EFCore.Benchmarks/ChangeTracker/DbSetOperationTests.cs).

CI/CD14pt85

CI is configured (.github/workflows/Build.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 (benchmark/EFCore.Benchmarks/EFCore.Benchmarks.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files50 root entries
  • .agents
  • .azuredevops
  • .claude
  • .config
  • .devcontainer
    Good: Environment pinned via .devcontainer/docker-compose.yml.
  • .github
    Good: 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/Build.yml).
    Good: Dependabot covers 2 ecosystems (nuget, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: Security policy present.
  • .vscode
  • benchmark
    Good: Test files detected (benchmark/EFCore.Benchmarks/ChangeTracker/DbSetOperationTests.cs).
    Good: Dependency manifest found (benchmark/EFCore.Benchmarks/EFCore.Benchmarks.csproj).
  • docs
  • eng
  • logo
  • rulesets
  • src
  • test
  • tools
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • activate.ps1
  • activate.sh
  • azure-pipelines-internal-tests.yml
  • azure-pipelines-public.yml
  • azure-pipelines.yml
  • build.cmd
  • build.sh
  • Directory.Build.props
  • Directory.Build.targets
  • Directory.Packages.props
  • EFCore.Cosmos.slnf
  • EFCore.Relational.slnf
  • EFCore.Runtime.slnf
  • EFCore.slnx
  • EFCore.slnx.DotSettings
  • EFCore.Sqlite.slnf
  • EFCore.Tools.slnf
  • es-metadata.yml
  • github-merge-flow.jsonc
  • global.json
  • helix.cmd
  • helix.sh
  • LICENSE.txt
    Good: Licensed under MIT.
  • Microsoft.Data.Sqlite.slnf
  • NuGet.config
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
  • restore.cmd
  • restore.sh
  • startvs.cmd
  • stylecop.json
  • test.cmd
  • test.sh