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

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

Documentation

88

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt85

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/check-no-merge-label.yml).

Tests18pt80

Test files detected (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzerTests.cs).

Reproducibility6pt92

Lockfile present (src/libraries/System.Net.Http/tests/FunctionalTests/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzer.Tests.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files38 root entries
  • .azuredevops
  • .claude
  • .config
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/check-no-merge-label.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
    Good: .gitignore present.
  • docs
  • eng
    Good: Test files detected (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzerTests.cs).
    Good: Dependency manifest found (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzer.Tests.csproj).
  • src
    Good: Code of conduct present.
    Good: Lockfile present (src/libraries/System.Net.Http/tests/FunctionalTests/package-lock.json). Installs are reproducible.
  • .clang-format
  • .clang-tidy
  • .CodeQL.yml
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
  • .markdownlint.json
  • .vsconfig
  • build.cmd
  • Build.proj
  • build.sh
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Directory.Build.props
  • Directory.Build.rsp
  • Directory.Build.targets
  • Directory.Solution.props
  • dotnet.cmd
  • dotnet.sh
  • es-metadata.yml
  • github-merge-flow.jsonc
  • global.json
  • LICENSE.TXT
    Good: Licensed under MIT.
  • NuGet.config
  • PATENTS.TXT
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • THIRD-PARTY-NOTICES.TXT