Good community traction and solid fundamentals. Nearly in the top tier.

Hire the top 1% OSS engineers

Documentation

84

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

63

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Tests18pt80

Test files detected (test).

Reproducibility6pt80

Lockfile present (assets/pnpm-lock.yaml). Installs are reproducible.

CI/CD14pt85

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (assets/package.json).

Repository metadata5pt100

Repository has a description.

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)
  • 117
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 1,411
    Watchers

Responsiveness

  • 14d 14h
    Median issue response
  • <1h
    Median PR merge time
  • 90
    Open issues
Repository files26 root entries
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/elixir.yml).
  • assets
    Good: Lockfile present (assets/pnpm-lock.yaml). Installs are reproducible.
    Good: Dependency manifest found (assets/package.json).
  • config
  • lib
  • priv
  • rel
  • test
    Good: Test files detected (test).
  • .credo.exs
  • .dialyzer_ignore.exs
  • .dockerignore
  • .env.example
  • .formatter.exs
  • .gitignore
    Good: .gitignore present.
  • .iex.exs
  • .tool-versions
  • coveralls.json
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • fiex
  • fly.toml
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • location.md
  • Makefile
  • mix.exs
  • mix.lock
  • 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.