93
/ 100
Well engineered for its size. A portfolio piece worth showing off.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 3Dependency manifest6pt
Add `description = "..."` to [package]. It appears in crates.io search results.
- 4Dependency manifest6pt
Add `license = "MIT"` (or your preferred SPDX identifier) to [package].
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
97
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Contributing guide is detailed and thorough.
Engineering
98
Lockfile present (bindings/node/package-lock.json). Installs are reproducible.
Test files detected (bindings/node/__test__/config.test.js).
CI is configured (.github/workflows/ci-minimal-features.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Issue or PR templates present.
Project health
70
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (Cargo.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 2Forks
- 19Releaseslatest 6mo ago
Community
- 85% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 16Watchers
Responsiveness
- 2d 19hMedian issue response
- 1hMedian PR merge time
- 55Open issues
Repository files36 root entries
- .agentsGood: Licensed under Apache-2.0.Good: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.Good: .gitignore present.
- .claude
- .githubGood: CI is configured (.github/workflows/ci-minimal-features.yml).Good: Issue or PR templates present.
- .superpowers
- bindingsGood: Test files detected (bindings/node/__test__/config.test.js).Good: Lockfile present (bindings/node/package-lock.json). Installs are reproducible.
- compaction-parity
- cqlite-cliGood: Environment pinned via cqlite-cli/tests/compatibility/docker/docker-compose.yml.
- cqlite-core
- cqlite-flight
- docs
- examples
- scripts
- test-data
- tests
- tools
- trino-connector
- website
- .clippy.toml
- .dockerignore
- .gitignore
- .pre-commit-config.yaml
- .rustfmt.toml
- AGENTS.md
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.md
- deny.toml
- LICENSE
- Makefile
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- rust-toolchain.toml
- SECURITY.mdGood: Security policy present.
- skills-lock.json
- tarpaulin.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/pmcfadin/cqlite)