97
/ 100
Polished work that hasn't found its audience yet.
A pseudo pip-search utility to ascertain if a package name is available in the PyPI repository and 'register' it
Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Contributing guide5pt
Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
94
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
98
Test files detected (pytest.ini).
CI is configured (.github/workflows/tests.yml).
Linter or formatter configured (.editorconfig).
Lockfile present (requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (pyproject.toml).
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)
- 1Forks
- 35Releaseslatest 3y ago
Community
- 100% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 6Watchers
Responsiveness
- 4hMedian issue response
- 13hMedian PR merge time
- 0Open issues
Repository files34 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/tests.yml).Good: Dependabot covers 3 ecosystems (github-actions, pip, pip). Dependencies stay current.Good: Issue or PR templates present.Good: Security policy present.
- assets
- data
- docs
- logs
- requirements
- src
- templates
- tests
- tools
- .coveragerc
- .deepsource.toml
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitconfig
- .gitignoreGood: .gitignore present.
- .gitmessage
- .pre-commit-config.yaml
- .prettierignore
- .readthedocs.yml
- AUTHORS.md
- CHANGELOG.md
- CITATION.cff
- DockerfileGood: Environment pinned via Dockerfile.
- jinja-genie.pkl
- LICENSEGood: Licensed under MIT.
- MANIFEST.in
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- pytest.iniGood: Test files detected (pytest.ini).
- 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.
- tasks.py
- templater.py
- tox.ini
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/stephen-ra-king/pynamer)