Popular for its size, but the engineering basics lag behind the interest.
Edalitcs
Documentation
78
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.
Licensed under AGPL-3.0.
Engineering
28
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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 package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
CI is configured (.github/workflows/docker-image.yml).
Linter or formatter configured (eda/eda_app/.editorconfig).
Project health
84
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 (eda/eda_api/package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 27Forks
- 5Releaseslatest 20d ago
Community
- —Community health
- —authors own >50% of commits
- 199Watchers
Responsiveness
- 62d 14hMedian issue response
- 7d 21hMedian PR merge time
- 14Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/docker-image.yml).
- docs
- edaGood: Linter or formatter configured (eda/eda_app/.editorconfig).Good: Dependency manifest found (eda/eda_api/package.json).
- .gitignoreGood: .gitignore present.
- DockerfileGood: Environment pinned via Dockerfile.
- Dockerfile_manual
- LICENSE.txtGood: Licensed under AGPL-3.0.
- 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.Good: README documents how to run the project.