Popular for its size, but the engineering basics lag behind the interest.
Run Time for AIE and FPGA based platforms
Documentation
43
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under Other.
Engineering
58
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.
CI is configured (.github/workflows/build-linux-gcc16-docker.yml).
Test files detected (src/runtime_src/core/common/runner/test).
Issue or PR templates present.
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)
- 535Forks
- 46Releaseslatest 6y ago
Community
- —Community health
- —authors own >50% of commits
- 669Watchers
Responsiveness
- 17d 7hMedian issue response
- 12hMedian PR merge time
- 153Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/build-linux-gcc16-docker.yml).Good: Issue or PR templates present.
- build
- srcGood: Test files detected (src/runtime_src/core/common/runner/test).
- tests
- .clangd
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .travis.yml
- CHANGELOG.rst
- CMakeLists.txt
- CONTRIBUTING.rstGood: 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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSEGood: Licensed under Other.
- NOTICE
- pyrightconfig.json
- README.rstGood: 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.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.