nickna/sharpts
Grade a repo

81

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and setup instructions.

Top 32% of 5,156 graded repos

Compile TypeScript to .NET IL; Use .NET classes in Typescript

Documentation77
Engineering75
Health100
C#156MIT11d ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  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

77

Install and run instructions9pt45

README documents how to install the project.

README12pt80

README is present.

License6pt100

Licensed under MIT.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

75

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.

Tests18pt80

Test files detected (tests).

CI/CD14pt85

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

Reproducibility6pt92

Lockfile present (extensions/vscode-sharpts/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (SharpTS.sln).

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)
  • 4
    Forks
  • 8
    Releaseslatest 1mo ago

Community

  • 57% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 156
    Watchers

Responsiveness

  • 1d 1h
    Median issue response
  • <1h
    Median PR merge time
  • 149
    Open issues
Repository files29 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for github-actions.
  • benchmarks
    Good: Environment pinned via benchmarks/gc-profiles/Dockerfile.
  • distribution
  • docs
  • eng
  • extensions
    Good: Lockfile present (extensions/vscode-sharpts/package-lock.json). Installs are reproducible.
  • external
  • samples
  • scripts
  • src
  • tests
    Good: Test files detected (tests).
  • .bun-version
  • .coderabbit.yaml
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .node-version
  • ARCHITECTURE.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Directory.Build.props
  • Directory.Packages.props
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SharpTS.sln
    Good: Dependency manifest found (SharpTS.sln).
  • STATUS.md
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/nickna/sharpts)](https://www.repo-grade.com/report/nickna/sharpts)

More graded C# repos