0
/ 100
Rough and inactive. Tests, CI, and a fuller README would revive it.
high performance, high scalability and high reliability database for IoT & big data
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (77).
See your top fixesTop 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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
76
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 is present.
README documents how to install the project.
A license file is present.
Engineering
54
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/test.yml).
Test files detected (3rd_party/MessagePack/test).
Issue or PR templates present.
Project health
64
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Repository has a description.
Dependency manifest found (3rd_party/MessagePack/msgpack_vc8.sln).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Issue or PR templates present.
- 3rd_partyGood: A license file is present.Good: Test files detected (3rd_party/MessagePack/test).Good: Dependency manifest found (3rd_party/MessagePack/msgpack_vc8.sln).Good: .gitignore present.
- bin
- conf
- debian
- docs
- installer
- java_client
- log
- sampleGood: Environment pinned via sample/docker/Dockerfile.
- server
- utility
- APACHE-2.0.txt
- bootstrap.sh
- CLA_rev1.1.pdf
- configure.ac
- EULA for GridDB Community Edition.pdf
- GCLA.md
- GNU-AGPL-3.0.txt
- Makefile.am
- README_ja.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tarasik-karasik/griddb_nosql)