61
/ 100
Early stage. Tests, CI, and a strong README would raise this score quickly.
暂无描述
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 B (80).
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 section showing how to install dependencies.
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
65
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
Licensed under Apache-2.0.
Engineering
49
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 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.
Test files detected (abc2program/tests).
Lockfile present (static_core/plugins/ets/tests/debugger/poetry.lock). Installs are reproducible.
Linter or formatter configured (libabckit/eslint.config.js).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (libabckit/package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 53 / 304Commits (30d / 90d)
- 9Forks
- 0Releases
Community
- 50% - FairCommunity health
- 11 bus factorauthors own >50% of commits
- 5Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 1Open issues
Repository files44 root entries
- .gitee
- abc2programGood: Test files detected (abc2program/tests).
- ark_guard
- arkplatform
- assembler
- bytecode_optimizer
- cmake
- common_interfaces
- compiler
- disassembler
- docs
- gn
- isa
- ldscripts
- libabckitGood: Linter or formatter configured (libabckit/eslint.config.js).Good: Dependency manifest found (libabckit/package.json).
- libark_defect_scan_aux
- libpandabase
- libpandafile
- libziparchive
- panda
- panda_guard
- pandastdlib
- platforms
- plugins
- scripts
- static_coreGood: Lockfile present (static_core/plugins/ets/tests/debugger/poetry.lock). Installs are reproducible.Good: Environment pinned via static_core/plugins/ets/playground/backend/Dockerfile.
- .clang-format
- .clang-tidy
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS_dyn.md
- AGENTS.md
- ark_config.gni
- ark_root.gni
- AUTHORS
- BUILD.gn
- bundle.json
- CMakeLists.txt
- codecheck_ignore.json
- CODEOWNERS
- LICENSEGood: Licensed under Apache-2.0.
- OAT.xml
- 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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/openharmony/arkcompiler_runtime_core)