ubugeeei-prod/vize
Grade a repo

93

/ 100

GradeA

Excellent work. The main thing left to polish is dependency metadata.

Top 10% of 5,156 graded repos

blazing fast Vue.js toolchain. compiler, linter, type checker, formatter, lsp, story system, editors. already 30k+ tests.

Documentation89
Engineering96
Health86
Rust925MITtoday

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

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

89

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

96

Reproducibility6pt70

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

Tests18pt100

Test files detected (crates/vize/src/commands/check/imports/registration/reachability/tests).

CI/CD14pt100

CI is configured (.github/workflows/build-docs.yml).

Linting and formatting5pt100

Linter or formatter configured (upstream/forks/lightningcss/rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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

  • 4393 / 8249
    Commits (30d / 90d)
  • 54
    Forks
  • 638
    Releaseslatest 9mo ago

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 925
    Watchers

Responsiveness

  • 75d 1h
    Median issue response
  • 1h
    Median PR merge time
  • 137
    Open issues
Repository files35 root entries
  • .cargo
  • .config
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: CI is configured (.github/workflows/build-docs.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • assets
  • crates
    Good: Test files detected (crates/vize/src/commands/check/imports/registration/reachability/tests).
  • davinci
  • docs
  • editors
  • examples
  • jsr
  • npm
  • patches
  • playground
  • tests
  • tools
  • upstream
    Good: Linter or formatter configured (upstream/forks/lightningcss/rustfmt.toml).
  • .coderabbit.yaml
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • default.nix
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • 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.
  • rust-toolchain.toml
  • socket.yml
  • tsconfig.json
  • vite.config.ts
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/ubugeeei-prod/vize)](https://www.repo-grade.com/report/ubugeeei-prod/vize)

More graded Rust repos