pnp/powershell

0

/ 100

Documentation68
Engineering58
Health100
C#883MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

PnP PowerShell

Documentation

68

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

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

README12pt78

README is present.

License6pt100

Licensed under MIT.

Engineering

58

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

CI/CD14pt57

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

Tests18pt80

Test files detected (src/Tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/ALC/PnP.PowerShell.ALC.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

  • —
    Commits (30d / 90d)
  • 406
    Forks
  • 21
    Releaseslatest 3y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 883
    Watchers

Responsiveness

  • 20h
    Median issue response
  • 12h
    Median PR merge time
  • 63
    Open issues
Repository files27 root entries
  • .claude
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/builddocsite.yml).
    Good: Issue or PR templates present.
  • .vscode
  • build
  • docker
  • documentation
  • pages
  • resources
  • samples
  • src
    Good: Test files detected (src/Tests).
    Good: Dependency manifest found (src/ALC/PnP.PowerShell.ALC.csproj).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • context7.json
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
  • dependencies.json
  • dotnetfoundation_v4_small.png
  • LICENSE
    Good: Licensed under MIT.
  • MIGRATE-1.0-to-2.0.md
  • MIGRATE-2.0-to-3.0.md
  • nugeticon.png
  • powershell
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
  • version.json
  • version.txt