pnp/pnpcore
Grade a repo

89

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 14% of 5,156 graded repos

The PnP Core SDK is a modern .NET SDK designed to work for Microsoft 365. It provides a unified object model for working with SharePoint Online and Teams which is agnostic to the underlying API's being called

Documentation85
Engineering87
Health100
C#355MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

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

85

Contributing guide5pt58

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

87

Tests18pt80

Test files detected (src/sdk/PnP.Core.Admin.Test/Microsoft365/TenantTests.cs).

CI/CD14pt85

CI is configured (.github/workflows/buildandtest.yml).

Reproducibility6pt90

Lockfile present (src/assets/pnpcoresdk-test-app/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

.NET formatting configured (src/assets/pnpcoresdk-test-app/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (samples/Demo.ASPNetCore/Demo.ASPNetCore.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

  • 35 / 108
    Commits (30d / 90d)
  • 226
    Forks
  • 17
    Releaseslatest 3y ago

Community

  • 100% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 355
    Watchers

Responsiveness

  • 6d 22h
    Median issue response
  • 3h
    Median PR merge time
  • 45
    Open issues
Repository files14 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/buildandtest.yml).
    Good: Dependabot covers 3 ecosystems (nuget, github-actions, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • build
  • docs
  • samples
    Good: Dependency manifest found (samples/Demo.ASPNetCore/Demo.ASPNetCore.csproj).
  • src
    Good: Test files detected (src/sdk/PnP.Core.Admin.Test/Microsoft365/TenantTests.cs).
    Good: .NET formatting configured (src/assets/pnpcoresdk-test-app/.editorconfig).
    Good: Lockfile present (src/assets/pnpcoresdk-test-app/package-lock.json). Installs are reproducible.
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • 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.
    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.
  • version.debug.increment
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/pnp/pnpcore)](https://www.repo-grade.com/report/pnp/pnpcore)

More graded C# repos