Good community traction and solid fundamentals. Nearly in the top tier.
Hire the top 1% OSS engineers
Documentation
84
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.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
63
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.
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.
Test files detected (test).
Lockfile present (assets/pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/elixir.yml).
Project health
100
Dependency manifest found (assets/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 117Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1,411Watchers
Responsiveness
- 14d 14hMedian issue response
- <1hMedian PR merge time
- 90Open issues
Repository files26 root entries
- .cursor
- .githubGood: CI is configured (.github/workflows/elixir.yml).
- assetsGood: Lockfile present (assets/pnpm-lock.yaml). Installs are reproducible.Good: Dependency manifest found (assets/package.json).
- config
- lib
- priv
- rel
- testGood: Test files detected (test).
- .credo.exs
- .dialyzer_ignore.exs
- .dockerignore
- .env.example
- .formatter.exs
- .gitignoreGood: .gitignore present.
- .iex.exs
- .tool-versions
- coveralls.json
- DockerfileGood: Environment pinned via Dockerfile.
- fiex
- fly.toml
- LICENSEGood: Licensed under AGPL-3.0.
- location.md
- Makefile
- mix.exs
- mix.lock
- README.mdGood: 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.