0
/ 100
Early stage. Tests, CI, and a strong README would raise this score quickly.
Testlum Codeless Runtime Engine Demo
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 B (81).
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
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.
A license file is present.
Engineering
51
No Java/Kotlin linter configured.
→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.
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.
CI is configured (.github/workflows/test.yml).
Test files detected (REGRESSION/resources/scenarios/websocket/stomp/subscribe/test).
Lockfile present (TEST-UI/package-lock.json). Installs are reproducible.
Project health
94
.gitignore present.
Dependency manifest found (TEST-API/pom.xml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 8Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 2Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).
- dockerGood: Environment pinned via docker/init-data/elasticsearch/Dockerfile.Issue: Build artifacts or local files may be committed (docker/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- REGRESSIONGood: Test files detected (REGRESSION/resources/scenarios/websocket/stomp/subscribe/test).
- TEST-APIGood: Dependency manifest found (TEST-API/pom.xml).
- TEST-UIGood: A license file is present.Good: Lockfile present (TEST-UI/package-lock.json). Installs are reproducible.
- .gitignoreGood: .gitignore present.
- 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.
- run-android-device
- run-app
- run-regression
- todoist-v10864.apk
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/testlumframework/demo)