0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
终末地 End Field Automation 基于ok-script开发的自动化
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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
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 AGPL-3.0.
Engineering
62
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.
CI is configured (.github/workflows/build.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Test files detected (tests).
Issue or PR templates present.
Project health
100
Dependency manifest found (requirements.txt).
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)
- 28Forks
- 321Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 510Watchers
Responsiveness
- <1hMedian issue response
- 2hMedian PR merge time
- 3Open issues
Repository files29 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- assets
- docs
- i18n
- icons
- scripts
- src
- target_doc
- testsGood: Test files detected (tests).
- tools
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .update_repo_gitignore
- auto_release.ps1
- auto_release.py
- auto_release.sh
- deploy.txt
- FUNDING.yml
- LICENSEGood: Licensed under AGPL-3.0.
- main_debug.py
- main.py
- ok_templates
- pyappify.yml
- README_en.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
- requirements.in
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- run_tests.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/alicejump/ok-end-field)