eclipse-dirigible/dirigible
Grade a repo

0

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 12% of 5,156 graded repos

Eclipse Dirigible™ Project

Documentation93
Engineering87
Health94
JavaScript277EPL-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under EPL-2.0.

Engineering

87

Tests18pt80

Test files detected (build/application/src/test).

CI/CD14pt85

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

Reproducibility6pt92

Lockfile present (components/resources/resources-dev-tools/src/main/resources/META-INF/dirigible/dev-tools/sdk/wasm_source_map/Cargo.lock). Installs are reproducible.

Linting and formatting5pt100

Java/Kotlin linting configured (components/resources/resources-dev-tools/src/main/resources/META-INF/dirigible/dev-tools/sdk/wasm_source_map/rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (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)
  • 96
    Forks
  • 531
    Releaseslatest 8y ago

Community

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

Responsiveness

  • 38d 3h
    Median issue response
  • <1h
    Median PR merge time
  • 470
    Open issues
Repository files34 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot configured for maven.
    Good: Issue or PR templates present.
  • .reuse
  • build
    Good: Test files detected (build/application/src/test).
    Good: Environment pinned via build/application/Dockerfile.
  • cli
  • components
    Good: Java/Kotlin linting configured (components/resources/resources-dev-tools/src/main/resources/META-INF/dirigible/dev-tools/sdk/wasm_source_map/rustfmt.toml).
    Good: Lockfile present (components/resources/resources-dev-tools/src/main/resources/META-INF/dirigible/dev-tools/sdk/wasm_source_map/Cargo.lock). Installs are reproducible.
  • dependencies
  • LICENSES
  • logo
  • misc
  • modules
  • npm
  • open-telemetry
    Issue: Build artifacts or local files may be committed (open-telemetry/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • samples
  • tests
  • .gitignore
    Good: .gitignore present.
  • CLAUDE_BPMN.md
  • CLAUDE_FEATURES.md
  • CLAUDE_UI.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • dirigible-formatter.xml
  • epl-v20.html
  • findbugs-exclude.xml
  • HARMONIA_RUNTIME_PLAN.md
  • INTENT_DRIVEN_APPLICATION_DEVELOPMENT_MANIFESTO.md
  • LICENSE
    Good: Licensed under EPL-2.0.
  • licensing-header.txt
  • notice.html
  • NOTICE.txt
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/eclipse-dirigible/dirigible)](https://www.repo-grade.com/report/eclipse-dirigible/dirigible)

More graded JavaScript repos