finos/morphir

0

/ 100

Documentation75
Engineering98
Health79
Rust199Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

A universal language for business and technology

Documentation

75

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

98

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (.config/mise/tasks/ecosystem/test_morphir_moonbit.py).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (website/.prettierrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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)
  • 65
    Forks
  • 9
    Releaseslatest 5mo ago

Community

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

Responsiveness

  • 6h
    Median issue response
  • <1h
    Median PR merge time
  • 154
    Open issues
Repository files37 root entries
  • .beads
    Good: .gitignore present.
  • .claude
    Good: Licensed under Apache-2.0.
  • .config
    Good: Test files detected (.config/mise/tasks/ecosystem/test_morphir_moonbit.py).
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • .morphir
  • crates
  • docs
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • ecosystem
  • examples
  • tests
  • website
    Good: Linter or formatter configured (website/.prettierrc.json).
    Issue: Build artifacts or local files may be committed (website/static/img/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • wit
  • _config.yml
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
  • .gitmodules
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • CNAME
  • DEVELOPING.md
  • elm-tooling.json
  • elm.json
  • LICENSE
  • LICENSE.spdx
  • MAINTAINERS.md
  • netlify.toml
  • NOTES.md
  • NOTICE
  • package.json
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • renovate.json