microsoft/vscode-python-environments
Grade a repo

80

/ 100

GradeB

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

Top 32% of 5,156 graded repos

VS Code extension for Python environment and package management

Documentation93
Engineering66
Health94
TypeScript131MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

93

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

66

Tests18pt35

Test files detected (build/test_update_ext_version.py).

CI/CD14pt72

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

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Dependency manifest6pt82

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)
  • 48
    Forks
  • 19
    Releaseslatest 5mo ago

Community

  • 87% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 131
    Watchers

Responsiveness

  • 1d 20h
    Median issue response
  • 2h
    Median PR merge time
  • 115
    Open issues
Repository files29 root entries
  • .github
    Good: CI is configured (.github/workflows/test_plan_item_validator.yml).
    Good: Issue or PR templates present.
  • .vscode
  • analysis
  • api
  • build
    Good: Test files detected (build/test_update_ext_version.py).
  • docs
  • examples
  • files
  • images
  • src
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierrc.js
  • .vscode-test.mjs
  • .vscodeignore
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • eslint.config.mjs
  • icon.png
  • 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).
  • package.nls.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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
  • tsconfig.json
  • webpack.config.js
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/microsoft/vscode-python-environments)](https://www.repo-grade.com/report/microsoft/vscode-python-environments)

More graded TypeScript repos