0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
open source, cloud-native, graph-based query language
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
65
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
88
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Test files detected (apps/mql/cmd/login_test.go).
CI is configured (.github/workflows/test-report.yml).
Formatting enforced (.github/.golangci.yaml).
Lockfile present (go.sum). Installs are reproducible.
Project health
92
Dependency manifest found (go.mod).
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)
- 36Forks
- 403Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 402Watchers
Responsiveness
- 6d 7hMedian issue response
- 11hMedian PR merge time
- 255Open issues
Repository files52 root entries
- .claude
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: Licensed under Other.Good: CI is configured (.github/workflows/test-report.yml).Good: Formatting enforced (.github/.golangci.yaml).Good: Dependabot covers 2 ecosystems (github-actions, docker). Dependencies stay current.
- .vscode
- appsGood: Test files detected (apps/mql/cmd/login_test.go).
- checksums
- cli
- discovery
- docs
- examples
- exec
- internal
- llx
- logger
- metrics
- mqlc
- mqlx
- mrn
- providers
- providers-sdk
- sbom
- scripts
- shared
- test
- types
- utils
- vault
- _typos.toml
- .copywrite.hcl
- .gitignoreGood: .gitignore present.
- .golangci.yaml
- .goreleaser.yml
- CLAUDE.md
- DEVELOPMENT.md
- Dockerfile
- Dockerfile-ubi
- feature_string.go
- featureflag_test.go
- featureflags.go
- features_autoupdate.go
- features.go
- features.yaml
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSE
- Makefile
- mql_test.go
- mql.go
- prometheus.yml
- providers.yaml
- README.mdGood: 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.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.
- tools.go
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mondoohq/mql)