azure/iotedge
Grade a repo

69

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Top 47% of 5,156 graded repos

The IoT Edge OSS project

Documentation44
Engineering73
Health100
C#1,509MIT1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (86).

See your top fixes
Now
D
69
Potential
B
86

Top fixes

Highest-impact changes first, ranked by point weight

16 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

44

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt58

README is present.

License6pt100

Licensed under MIT.

Engineering

73

CI/CD14pt40

CI is configured (.github/workflows/issue-labeler.yml).

Tests18pt80

Test files detected (edge-agent/test).

Reproducibility6pt80

Lockfile present (edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/packages.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 (Microsoft.Azure.Devices.Edge.sln).

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

  • 8 / 25
    Commits (30d / 90d)
  • 473
    Forks
  • 246
    Releaseslatest 6y ago

Community

  • 75% - Good
    Community health
  • 8 bus factor
    authors own >50% of commits
  • 1,509
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 21h
    Median PR merge time
  • 95
    Open issues
Repository files41 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/issue-labeler.yml).
    Good: Issue or PR templates present.
  • .vscode
  • builds
  • doc
  • e2e_deployment_files
  • e2e_test_files
  • edge-agent
    Good: Test files detected (edge-agent/test).
    Good: Lockfile present (edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/packages.lock.json). Installs are reproducible.
    Good: Environment pinned via edge-agent/docker/linux/Dockerfile.
  • edge-hub
  • edge-modules
  • edge-util
  • edgelet
  • mqtt
  • samples
  • scripts
  • smoke
  • snap
  • test
  • tools
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • Azure.IoT.Edge.DotSettings
  • CHANGELOG.md
  • CodeCoverage.runsettings
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • Microsoft.Azure.Devices.Edge.sln
    Good: Dependency manifest found (Microsoft.Azure.Devices.Edge.sln).
  • Microsoft.Azure.Devices.Edge.sln.DotSettings
  • netcoreappVersion.props
  • nuget.config
  • owners.txt
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rust-toolchain.toml
  • SECURITY.md
    Good: Security policy present.
  • stylecop.json
  • stylecop.props
  • stylecop.ruleset
  • THIRDPARTYNOTICES
  • trademark.txt
  • versionInfo.json
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/azure/iotedge)](https://www.repo-grade.com/report/azure/iotedge)

More graded C# repos