azure/azure-sdk-for-c

0

/ 100

Documentation95
Engineering79
Health100
C242MITtoday
Grade a repo

Polished and well engineered. Punching above its star count.

This repository is for active development of the Azure SDK for Embedded C. For consumers of the SDK we recommend visiting our versioned developer docs at https://azure.github.io/azure-sdk-for-c.

Documentation

95

Contributing guide5pt85

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/event-processor.yml).

Tests18pt80

Test files detected (eng/scripts/tests).

Reproducibility6pt90

Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (eng/common/spelling/package.json).

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

  • 25 / 78
    Commits (30d / 90d)
  • 135
    Forks
  • 19
    Releaseslatest 5y ago

Community

  • 87% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 242
    Watchers

Responsiveness

  • 138d 23h
    Median issue response
  • 1d 2h
    Median PR merge time
  • 48
    Open issues
Repository files25 root entries
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/event-processor.yml).
    Good: Dependabot covers 2 ecosystems (vcpkg, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • .vscode-config
  • cmake-modules
  • doc
  • eng
    Good: Test files detected (eng/scripts/tests).
    Good: Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (eng/common/spelling/package.json).
  • samples
  • sdk
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • cgmanifest.json
  • CHANGELOG.md
  • CMakeLists.txt
  • CMakeSettings.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE.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.
    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.
  • SUPPORT.md
  • vcpkg.json