microsoft/semantic-kernel
Grade a repo

93

/ 100

GradeA

Exemplary work. Strong across project hygiene, documentation, and engineering.

Top 8% of 5,156 graded repos

Integrate cutting-edge LLM technology quickly and easily into your apps

Documentation97
Engineering88
Health100
C#28,367MIT15d ago

Top fixes

Highest-impact changes first, ranked by point weight

6 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

97

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

88

Tests18pt80

Test files detected (dotnet/samples/Concepts/ChatCompletion/ChatHistoryReducers/ChatHistoryReducerTests.cs).

CI/CD14pt85

CI is configured (.github/workflows/dotnet-build-and-test.yml).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Reproducibility6pt100

Lockfile present (dotnet/samples/Demos/ProcessFrameworkWithSignalR/package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (dotnet/samples/AgentFrameworkMigration/AgentOrchestrations/Step01_Concurrent/AgentOrchestrations_Step01_Concurrent.csproj).

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

  • 16 / 85
    Commits (30d / 90d)
  • 4,690
    Forks
  • 274
    Releaseslatest 3y ago

Community

  • 100% - Good
    Community health
  • 7 bus factor
    authors own >50% of commits
  • 28,367
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 7h
    Median PR merge time
  • 228
    Open issues
Repository files19 root entries
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/dotnet-build-and-test.yml).
    Good: Dependabot covers 3 ecosystems (nuget, pip, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • docs
  • dotnet
    Good: Test files detected (dotnet/samples/Concepts/ChatCompletion/ChatHistoryReducers/ChatHistoryReducerTests.cs).
    Good: Lockfile present (dotnet/samples/Demos/ProcessFrameworkWithSignalR/package-lock.json). Installs are reproducible.
    Good: Environment pinned via dotnet/samples/Demos/QualityCheck/python-server/docker-compose.yml.
    Good: Dependency manifest found (dotnet/samples/AgentFrameworkMigration/AgentOrchestrations/Step01_Concurrent/AgentOrchestrations_Step01_Concurrent.csproj).
  • java
  • prompt_template_samples
  • python
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • COMMUNITY.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.
    Good: Contributing guide describes code style expectations.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • FEATURE_MATRIX.md
  • LICENSE
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • TRANSPARENCY_FAQS.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/microsoft/semantic-kernel)](https://www.repo-grade.com/report/microsoft/semantic-kernel)

More graded C# repos