Popular for its size, but the engineering basics lag behind the interest.
New and extensible file format for storage of large columnar datasets.
Documentation
93
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
51
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 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.
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/linux-build.yml).
Test files detected (dwio/nimble/common/tests).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 84Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 718Watchers
Responsiveness
- 1d 4hMedian issue response
- <1hMedian PR merge time
- 130Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/linux-build.yml).Good: Dependabot configured for github-actions.
- CMake
- dwioGood: Test files detected (dwio/nimble/common/tests).
- scripts
- .clang-format
- .gersemirc
- .gitignoreGood: .gitignore present.
- .gitmodules
- .pre-commit-config.yaml
- AGENTS.md
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: 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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSEGood: Licensed under Apache-2.0.
- license.header
- Makefile
- openzl
- 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.
- velox