space-wizards/space-station-14
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

A multiplayer game about paranoia and chaos on a space station. Remake of the cult-classic Space Station 13.

Documentation87
Engineering85
Health100
C#3,673MITtoday

Documentation

87

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

85

Reproducibility6pt70

Lockfile present (Tools/markings/markings/go.sum). Installs are reproducible.

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)
  • 5,426
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 3,673
    Watchers

Responsiveness

  • 31d 1h
    Median issue response
  • 3h
    Median PR merge time
  • 4,282
    Open issues
Repository files70 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
  • Content.Docfx
    Good: Licensed under MIT.
  • 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.Tests
  • Content.Tools
  • Content.YAMLLinter
  • MSBuild
  • Pow3r
  • Resources
  • Tools
    Good: Lockfile present (Tools/markings/markings/go.sum). Installs are reproducible.
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .noai
  • 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.Packages.props
  • flake.lock
  • flake.nix
  • global.json
  • LICENSE.TXT
  • nuget.config
  • omnisharp.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.
  • RobustToolbox
  • RUN_THIS.py
  • run-build-debug.bat
  • run-build-debug.sh
  • run-build-release.bat
  • run-build-release.sh
  • run-build-tools.bat
  • run-build-tools.sh
  • run-client-debug.bat
  • run-client-debug.sh
  • run-client-nobuild.bat
  • run-client-nobuild.sh
  • run-client-release.bat
  • run-client-release.sh
  • run-client-tools.bat
  • run-client-tools.sh
  • run-nobuild.bat
  • run-nobuild.sh
  • run-server-debug.bat
  • run-server-debug.sh
  • run-server-nobuild.bat
  • run-server-nobuild.sh
  • run-server-release.bat
  • run-server-release.sh
  • run-server-tools.bat
  • run-server-tools.sh
  • SECURITY.md
    Good: Security policy present.
  • shell.nix
  • SpaceStation14.slnx
  • SpaceStation14.slnx.DotSettings