0
/ 100
Strong community interest, but tests, CI, or docs need work.
High-performance automatic differentiation of LLVM and MLIR.
Documentation
83
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
47
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/enzyme-ci.yml).
Test files detected (enzyme/test).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 169Forks
- 272Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 1,633Watchers
Responsiveness
- <1hMedian issue response
- 3hMedian PR merge time
- 278Open issues
Repository files11 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/enzyme-ci.yml).Good: Dependabot configured for github-actions.
- .packaging
- enzymeGood: Test files detected (enzyme/test).
- integration
- .gitattributes
- .gitignoreGood: .gitignore present.
- CITATION.bib
- CONTRIBUTING.mdGood: 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.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under Other.
- Readme.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.