0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

AI lifecycle platform where engineers and agents track experiments, train models, and ship to production.

Python198Apache-2.0today

Documentation

72

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.

README12pt68

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

61

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.

Tests18pt35

Test files detected (backend/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/[api-client] tests-and-linters.yml).

Linting and formatting5pt100

Linter or formatter configured (extras/js/packages/attachments/.editorconfig).

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

Housekeeping3pt60

.gitignore present.

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)
  • 2
    Forks
  • 2
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • 5d 3h
    Median PR merge time
  • 10
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/[api-client] tests-and-linters.yml).
  • .jules
  • backend
    Good: Test files detected (backend/tests).
    Good: Environment pinned via backend/Dockerfile.
  • dev
  • docs
    Issue: Build artifacts or local files may be committed (docs/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • extras
    Good: Linter or formatter configured (extras/js/packages/attachments/.editorconfig).
  • frontend
  • lumlflow
  • prisma
  • satellite
  • sdk
  • wasm
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.