Good shape overall. A few tweaks would push it into the top tier.
Compile TypeScript to .NET IL; Use .NET classes in Typescript
Documentation
97
README documents how to install the project.
README is present.
Licensed under MIT.
Contributing guide is detailed and thorough.
Engineering
62
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
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.
Lockfile present (Examples/NpmUuid/package-lock.json). Installs are reproducible.
Test files detected (SharpTS.Test262/SmokeTest.cs).
CI is configured (.github/workflows/ci.yml).
Project health
100
Dependency manifest found (SharpTS.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 3Forks
- 6Releaseslatest 4mo ago
Community
- —Community health
- —authors own >50% of commits
- 142Watchers
Responsiveness
- 1d 1hMedian issue response
- <1hMedian PR merge time
- 24Open issues
Repository files40 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- benchmarks
- Cli
- Compilation
- Declaration
- Diagnostics
- docs
- ExamplesGood: Lockfile present (Examples/NpmUuid/package-lock.json). Installs are reproducible.
- Execution
- external
- LspBridge
- Modules
- Packaging
- Parsing
- Repl
- Runtime
- scripts
- SharpTS.Microbenchmarks
- SharpTS.Sdk
- SharpTS.Sdk.Tasks
- SharpTS.Test262Good: Test files detected (SharpTS.Test262/SmokeTest.cs).
- SharpTS.Test262.Worker
- SharpTS.Tests
- SharpTS.TypeScriptConformance
- stdlib
- TypeSystem
- vscode-sharpts
- .gitignoreGood: .gitignore present.
- .gitmodules
- ARCHITECTURE.md
- CLAUDE.md
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- Program.cs
- README.mdGood: 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.
- SharpTS.csprojGood: Dependency manifest found (SharpTS.csproj).
- SharpTS.sln
- STATUS-NODE.md
- STATUS.md