azure/azure-sdk-for-ios

0

/ 100

Documentation63
Engineering77
Health100
Swift197MITtoday
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

iOS client SDKs for Microsoft Azure

Documentation

63

Install and run instructions9pt45

README documents how to install the project.

README12pt55

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

77

CI/CD14pt57

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

Reproducibility6pt70

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

Tests18pt80

Test files detected (sdk/communication/AzureCommunicationChat/Tests).

Linting and formatting5pt100

Linter or formatter configured (.swiftlint.yml).

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

  • —
    Commits (30d / 90d)
  • 106
    Forks
  • 143
    Releaseslatest 8y ago

Community

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

Responsiveness

  • 12h
    Median issue response
  • 20h
    Median PR merge time
  • 22
    Open issues
Repository files16 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/event-processor.yml).
    Good: Issue or PR templates present.
  • AzureSDK.xcworkspace
  • eng
    Good: Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (eng/common/spelling/package.json).
  • examples
  • jazzy
  • sdk
    Good: Test files detected (sdk/communication/AzureCommunicationChat/Tests).
  • .gitignore
    Good: .gitignore present.
  • .swiftformat
  • .swiftlint.yml
    Good: Linter or formatter configured (.swiftlint.yml).
  • 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.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under MIT.
  • Podfile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    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.
  • SUPPORT.md