77
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Azure SRE Agent is an AI-powered reliability assistant that helps teams diagnose and resolve production issues, reduce operational toil, and lower mean time to resolution
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
79
README is present.
CONTRIBUTING guide found.
README documents how to install the project.
Licensed under MIT.
Engineering
68
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
CI is configured (.github/workflows/validate-templates.yml).
Test files detected (sreagent-templates/tests).
Lockfile present (labs/zava-aks-postgres/src/api/package-lock.json). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (labs/deployment-compliance/src/api/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 60Forks
- 0Releases
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 125Watchers
Responsiveness
- 15hMedian issue response
- 2d 18hMedian PR merge time
- 70Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/validate-templates.yml).Good: Issue or PR templates present.
- appendix
- labsGood: Lockfile present (labs/zava-aks-postgres/src/api/package-lock.json). Installs are reproducible.Good: Environment pinned via labs/deployment-compliance/src/api/Dockerfile.Good: Dependency manifest found (labs/deployment-compliance/src/api/package.json).
- sreagent-templatesGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Test files detected (sreagent-templates/tests).
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- README.mdGood: 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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/microsoft/sre-agent)