82
/ 100
Good shape overall. A few tweaks would push it into the top tier.
OpenShift extension for Visual Studio Code
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 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
90
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
71
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/check-alizer.yml).
Test files detected (.mocharc.js).
Linter or formatter configured (.editorconfig).
Lockfile present (package-lock.json). Installs are reproducible.
Project health
98
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)
- 63Forks
- 68Releaseslatest 7y ago
Community
- 50% - FairCommunity health
- -authors own >50% of commits
- 120Watchers
Responsiveness
- 33d 6hMedian issue response
- <1hMedian PR merge time
- 110Open issues
Repository files31 root entries
- .githubGood: CI is configured (.github/workflows/check-alizer.yml).Good: Dependabot covers 2 ecosystems (github-actions, npm). Dependencies stay current.
- .vscode
- build
- doc
- images
- resources
- schemas
- src
- test
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mocharc.jsGood: Test files detected (.mocharc.js).
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierrc
- .vscodeignore
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- coverconfig.json
- DCO
- eslint.config.mjs
- header.js
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.commands.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.crc-workflow.md
- README.md
- README.serverlessfn.md
- tsconfig.json
- USAGE_DATA.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/redhat-developer/vscode-openshift-tools)