jortilles/eda

0

/ 100

TypeScript199AGPL-3.01d ago
Grade a repo

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

Edalitcs

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

Licensed under AGPL-3.0.

Engineering

28

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

CI/CD14pt57

CI is configured (.github/workflows/docker-image.yml).

Linting and formatting5pt100

Linter or formatter configured (eda/eda_app/.editorconfig).

Project health

84

Repository metadata5pt40

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 manifest6pt100

Dependency manifest found (eda/eda_api/package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 27
    Forks
  • 5
    Releaseslatest 20d ago

Community

  • Community health
  • authors own >50% of commits
  • 199
    Watchers

Responsiveness

  • 62d 14h
    Median issue response
  • 7d 21h
    Median PR merge time
  • 14
    Open issues
Repository files8 root entries
  • .github
    Good: CI is configured (.github/workflows/docker-image.yml).
  • docs
  • eda
    Good: Linter or formatter configured (eda/eda_app/.editorconfig).
    Good: Dependency manifest found (eda/eda_api/package.json).
  • .gitignore
    Good: .gitignore present.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile_manual
  • LICENSE.txt
    Good: Licensed under AGPL-3.0.
  • 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.