Strong community interest, but tests, CI, or docs need work.
ABC: System for Sequential Logic Synthesis and Formal Verification
Documentation
76
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 Other.
Engineering
46
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.github/workflows/build-posix-cmake.yml).
Test files detected (src/base/test).
Project health
100
Dependency manifest found (.github/scripts/abcspace.sln).
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)
- 765Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1,187Watchers
Responsiveness
- 4hMedian issue response
- 9hMedian PR merge time
- 227Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/build-posix-cmake.yml).Good: Dependency manifest found (.github/scripts/abcspace.sln).
- lib
- srcGood: Licensed under Other.Good: Test files detected (src/base/test).
- test
- .gitattributes
- .gitcommit
- .gitignoreGood: .gitignore present.
- .hgignore
- abc.rc
- abcexe.dsp
- abclib.dsp
- abcspace.dsw
- arch_flags.c
- CMakeLists.txt
- copyright.txt
- depends.sh
- i10.aig
- Makefile
- README.mdGood: 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.Good: README documents how to install the project.Good: README documents how to run the project.
- readmeaig