82
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Ascend PyTorch adapter (torch_npu). Mirror of https://gitcode.com/Ascend/pytorch
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 a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
97
README documents how to install the project.
README is present.
Licensed under Other.
Contributing guide is detailed and thorough.
Engineering
66
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-and-test.yml).
Test files detected (ci/access_control/strategy/test_file.py).
Lockfile present (requirements.txt). Installs are reproducible.
Linter or formatter configured (.editorconfig).
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)
- 76Forks
- 0Releases
Community
- 50% - FairCommunity health
- 8 bus factorauthors own >50% of commits
- 542Watchers
Responsiveness
- 7d 14hMedian issue response
- 9d 21hMedian PR merge time
- 111Open issues
Repository files41 root entries
- .ci
- .gitcode
- .githubGood: CI is configured (.github/workflows/_build-and-test.yml).
- ciGood: Test files detected (ci/access_control/strategy/test_file.py).Good: Environment pinned via ci/docker/ARM/Dockerfile.
- cmake
- docker
- docs
- examples
- figures
- test
- third_party
- tools
- torch_npu
- torchnpugen
- .clang-format
- .clang-tidy
- .cmakelintrc
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .flake8
- .gitignoreGood: .gitignore present.
- .gitmodules
- .lintrunner.toml
- build_libtorch_npu.py
- CMakeLists.txt
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- env.sh
- generate_code.sh
- LICENSEGood: Licensed under Other.
- mypy-strict.ini
- mypy.ini
- OWNERS
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- pyrefly.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.
- README.zh.md
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- SECURITYNOTE.md
- setup.cfg
- setup.py
- Third_Party_Open_Source_Software_Notice
- version.txt
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ascend/pytorch)