A well-known project done right. Strong docs and solid engineering throughout.

A refined collection of Hypervelocity Engineering components (instructions, prompts, agents, and skills) to start your project off right, or upgrade your existing projects to get the most out of GitHub Copilot

Outstanding. A score of 96/100 puts this repo in a very small tier of truly well-engineered projects.

Documentation

99

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

91

Tests18pt80

Test files detected (.github/skills/accessibility/accessibility/tests).

Reproducibility6pt90

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

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (docs/docusaurus/eslint.config.mjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 214
    Forks
  • 24
    Releaseslatest 4mo ago

Community

  • Community health
  • authors own >50% of commits
  • 1,198
    Watchers

Responsiveness

  • 71d 5h
    Median issue response
  • 3d 12h
    Median PR merge time
  • 453
    Open issues
Repository files37 root entries
  • .cspell
  • .devcontainer
  • .github
    Good: Test files detected (.github/skills/accessibility/accessibility/tests).
    Good: CI is configured (.github/workflows/devcontainer-lockfile-check.yml).
    Good: Dependabot covers 3 ecosystems (npm, github-actions, uv). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: Security policy present.
  • .vscode
  • collections
  • docs
    Good: Linter or formatter configured (docs/docusaurus/eslint.config.mjs).
  • evals
  • extension
  • logs
  • plugins
  • scripts
  • .cspell.json
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .markdownlint-cli2.jsonc
  • .markdownlint.json
  • .npmrc
  • .release-please-manifest.json
  • .syft.yaml
  • .vally.yaml
  • audit-ci.json
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • 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.
  • GOVERNANCE.md
  • justfile
  • 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.md
    Good: 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.
  • release-please-config.json
  • SECURITY.md
  • SUPPORT.md
  • THIRD-PARTY-NOTICES
  • TRANSPARENCY-NOTE.md