Solid engineering. The main gap is visibility.
My test to a new version of the UPVfab SiN PDK
Documentation
67
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 MIT.
Engineering
74
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 poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/test_code.yml).
Test files detected (tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Project health
71
Last pushed 6-12 months ago (−60 pts).
→ A recent commit signals the project is still maintained.
Repository has a description.
Dependency manifest found (pyproject.toml).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/test_code.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.
- .vscode
- docs
- testsGood: Test files detected (tests).
- training
- upvfab
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .sourcery.yaml
- CHANGELOG.md
- install_tech.py
- LICENSEGood: Licensed under MIT.
- Makefile
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Good: README is well structured with multiple sections.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.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.