81
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
Let VSCode support previewing PDF, Excel, Word and other formats, and add markdown WYSIWYG editor.
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
89
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
68
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/main.yml).
Test files detected (test).
Linter or formatter configured (.eslintrc.js).
Issue or PR templates present.
Project health
100
Dependency manifest found (package.json).
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)
- 185Forks
- 0Releases
Community
- 57% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,415Watchers
Responsiveness
- 5d 20hMedian issue response
- 23hMedian PR merge time
- 123Open issues
Repository files32 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Issue or PR templates present.
- .vscode
- docs
- iconsGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- image
- lib
- public
- resource
- snippets
- src
- syntaxes
- template
- testGood: Test files detected (test).
- theme
- vditor
- vite
- .eslintrc_react.cjs
- .eslintrc.jsGood: Linter or formatter configured (.eslintrc.js).
- .gitignoreGood: .gitignore present.
- .vscodeignore
- build.ts
- changelog.md
- index.html
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README-CN.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.
- README-TW.md
- README.md
- shortcut.md
- telemetry.json
- tsconfig.json
- vite.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/cweijan/vscode-office)