Good shape overall. A few tweaks would push it into the top tier.

OpenShift extension for Visual Studio Code

Documentation

90

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

71

Issue and PR templates6pt0

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/CD14pt40

CI is configured (.github/workflows/check-alizer.yml).

Tests18pt100

Test files detected (.mocharc.js).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Project health

98

Dependency manifest6pt93

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 63
    Forks
  • 68
    Releaseslatest 7y ago

Community

  • Community health
  • authors own >50% of commits
  • 120
    Watchers

Responsiveness

  • 33d 6h
    Median issue response
  • <1h
    Median PR merge time
  • 109
    Open issues
Repository files31 root entries
  • .github
    Good: 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
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mocharc.js
    Good: Test files detected (.mocharc.js).
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierrc
  • .vscodeignore
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: 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
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.commands.md
    Good: 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