Good shape overall. A few tweaks would push it into the top tier.
LISA is developed and maintained by Microsoft, to empower Linux validation.
Documentation
59
README is present.
README documents how to install the project.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
Licensed under MIT.
Engineering
85
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
Test files detected (docs/tools/test_spec_gen.py).
CI is configured (.github/workflows/ai-test-selection-cancel-cleanup.yml).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
Project health
91
.gitignore present.
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 236Forks
- 184Releaseslatest 4y ago
Community
- —Community health
- —authors own >50% of commits
- 331Watchers
Responsiveness
- 6d 19hMedian issue response
- 11hMedian PR merge time
- 67Open issues
Repository files18 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/ai-test-selection-cancel-cleanup.yml).Good: Issue or PR templates present.
- docsIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.Good: Test files detected (docs/tools/test_spec_gen.py).
- installers
- lisaGood: Environment pinned via lisa/microsoft/testsuites/docker/TestScripts/docker-compose.yml.
- selftests
- typings
- .envIssue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitattributes
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- MANIFEST.in
- noxfile.py
- pylintrc
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- readthedocs.yaml
- SECURITY.mdGood: Security policy present.