0
/ 100
Polished and well engineered. Punching above its star count.
Twinkle✨: Training workbench to make your model glow.
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.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Dependency manifest6pt
Add a [project.urls] table (Homepage, Repository) so PyPI links back to your project.
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
95
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
82
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.
Lockfile present (poetry.lock). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/citest_npu.yaml).
Issue or PR templates present.
Project health
98
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)
- 33Forks
- 8Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 241Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 5Open issues
Repository files26 root entries
- .dev_scripts
- .githubGood: CI is configured (.github/workflows/citest_npu.yaml).Good: Issue or PR templates present.Good: Security policy present.
- assets
- client_tools
- cmake
- cookbook
- docs
- notebook
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING_CN.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.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.Good: Contributing guide includes code examples.
- DockerfileGood: Environment pinned via Dockerfile.
- INSTALL_CLIENT.ps1
- INSTALL_CLIENT.sh
- INSTALL_MEGATRON.sh
- LICENSEGood: Licensed under Apache-2.0.
- poetry.lockGood: Lockfile present (poetry.lock). Installs are reproducible.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README_ZH.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.
- README.md
- ROADMAP.md
- setup.cfg
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/modelscope/twinkle)