0

/ 100

GradeC

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

An open source project aimed at creating unique mechanics and a pleasant game atmosphere in the game Space Station 14

Documentation

60

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

Add setup instructions, code style notes, and how to run tests.

README12pt85

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

License6pt100

Licensed under MIT.

Engineering

76

Reproducibility6pt0

No dependency lockfile found (−70 pts).

Enable and commit packages.lock.json so NuGet restores are repeatable.

Tests18pt80

Test files detected (Content.IntegrationTests/Fixtures/GameTest.cs).

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (BuildChecker/BuildChecker.csproj).

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)
  • 497
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 103
    Watchers

Responsiveness

  • 2d 8h
    Median issue response
  • 2h
    Median PR merge time
  • 238
    Open issues
Repository files38 root entries
  • .github
    Good: CI is configured (.github/workflows/build-docfx.yml).
    Good: Issue or PR templates present.
  • .run
  • .vscode
  • BuildChecker
    Good: Dependency manifest found (BuildChecker/BuildChecker.csproj).
  • BuildFiles
  • Content.Benchmarks
  • Content.Client
    Good: Licensed under MIT.
  • Content.Docfx
  • Content.IntegrationTests
    Good: Test files detected (Content.IntegrationTests/Fixtures/GameTest.cs).
  • Content.MapRenderer
  • Content.Packaging
  • Content.PatreonParser
  • Content.Replay
  • Content.Server
  • Content.Server.Database
  • Content.Shared
  • Content.Shared.Database
  • Content.Starlight.Codegen
  • Content.Tests
  • Content.Tools
  • Content.YAMLLinter
  • MSBuild
  • Pow3r
  • Resources
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
  • Directory.Build.targets
  • Directory.Packages.props
  • LICENSE-Starlight.TXT
  • LICENSE.TXT
  • MAP_FIX.py
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • RUN_THIS.py