rising622/vscode

0

/ 100

Documentation86
Engineering95
Health47
0MIT3y ago
Grade a repo

Solid engineering. The main gap is visibility.

Visual Studio Code

Documentation

86

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

95

CI/CD14pt85

CI is configured (.github/workflows/ci.yml).

Reproducibility6pt92

Lockfile present (yarn.lock). Installs are reproducible.

Tests18pt100

Test files detected (build/lib/test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

47

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files35 root entries
  • .devcontainer
  • .eslintplugin
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .vscode
  • build
    Good: Test files detected (build/lib/test).
  • cli
  • extensions
    Good: Environment pinned via extensions/vscode-colorize-tests/test/colorize-fixtures/Dockerfile.
    Issue: Build artifacts or local files may be committed (extensions/css-language-features/server/test/linksTestFixtures/node_modules/foo) (−40 pts).Fix: Remove them and add to .gitignore.
  • remote
  • resources
  • scripts
  • src
  • test
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore
  • .eslintrc.json
  • .git-blame-ignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lsifrc.json
  • .mailmap
  • .mention-bot
  • .nvmrc
  • .yarnrc
  • cglicenses.json
  • cgmanifest.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • gulpfile.js
  • LICENSE.txt
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • product.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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • ThirdPartyNotices.txt
  • tsfmt.json
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.