0
/ 100
Hugely popular, but the engineering hasn't kept pace — start with CI and a license.
Python - 100天从新手到大师
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (74).
See your top fixesTop 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.
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
59
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
38
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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.
Lockfile present (公开课/年薪50W+的Python程序员如何写代码/code/Python/opencourse/requirements.txt). Installs are reproducible.
Test files detected (Day31-35/code/test_example01.py).
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (公开课/年薪50W+的Python程序员如何写代码/code/Python/opencourse/requirements.txt).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 1Commits (30d / 90d)
- 55,682Forks
- 0Releases
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 184,049Watchers
Responsiveness
- 6d 3hMedian issue response
- 9d 6hMedian PR merge time
- 702Open issues
Repository files16 root entries
- Day01-20
- Day21-30
- Day31-35Good: Test files detected (Day31-35/code/test_example01.py).
- Day36-45
- Day46-60
- Day61-65
- Day66-80
- Day81-90
- Day91-100
- res
- 公开课Good: Lockfile present (公开课/年薪50W+的Python程序员如何写代码/code/Python/opencourse/requirements.txt). Installs are reproducible.Good: Dependency manifest found (公开课/年薪50W+的Python程序员如何写代码/code/Python/opencourse/requirements.txt).
- 番外篇
- .gitignoreGood: .gitignore present.
- Python学习资源汇总.md
- 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.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.
- 更新日志.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jackfrued/python-100-days)