testlumframework/demo
Grade a repo

0

/ 100

GradeD

Early stage. Tests, CI, and a strong README would raise this score quickly.

Testlum Codeless Runtime Engine Demo

Documentation78
Engineering51
Health94
Java8today

Documentation

78

Contributing guide5pt0

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

51

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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/CD14pt40

CI is configured (.github/workflows/test.yml).

Tests18pt80

Test files detected (REGRESSION/resources/scenarios/websocket/stomp/subscribe/test).

Reproducibility6pt80

Lockfile present (TEST-UI/package-lock.json). Installs are reproducible.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (TEST-API/pom.xml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 8
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/test.yml).
  • docker
    Good: 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.
  • REGRESSION
    Good: Test files detected (REGRESSION/resources/scenarios/websocket/stomp/subscribe/test).
  • TEST-API
    Good: Dependency manifest found (TEST-API/pom.xml).
  • TEST-UI
    Good: A license file is present.
    Good: Lockfile present (TEST-UI/package-lock.json). Installs are reproducible.
  • .gitignore
    Good: .gitignore present.
  • README.md
    Good: 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