0
/ 100
Fresh project with a decent start. Tests and CI now will set it apart.
Documentation
82
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
26
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
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.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (pyproject.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 1Releaseslatest today
Community
- -Community health
- -authors own >50% of commits
- 9Watchers
Responsiveness
- -Median issue response
- 1hMedian PR merge time
- 0Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).
- dardcor_agent
- image
- pydardcorGood: Environment pinned via pydardcor/assets/monaco/vs/basic-languages/dockerfile.
- .gitignoreGood: .gitignore present.
- build.py
- dardcor
- Dardcor Code.spec
- dardcor.py
- installer.iss
- LICENSEGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- version_info.txt