paradisess13/paradise

0

/ 100

Documentation88
Engineering79
Health100
DM446AGPL-3.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Paradise Station's GitHub main repository.

Documentation

88

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

79

CI/CD14pt57

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

Tests18pt80

Test files detected (_maps/map_files/tests).

Reproducibility6pt92

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (rust/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

  • —
    Commits (30d / 90d)
  • 1,320
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 446
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 1h
    Median PR merge time
  • 975
    Open issues
Repository files38 root entries
  • _maps
    Good: Test files detected (_maps/map_files/tests).
  • .github
    Good: CI is configured (.github/workflows/build_rust.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .vscode
  • code
    Good: Licensed under AGPL-3.0.
  • config
  • docs
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
    Good: Code of conduct present.
  • html
  • icons
  • interface
  • rust
    Good: Lockfile present (rust/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (rust/Cargo.toml).
  • sound
  • SQL
  • strings
  • tgui
  • tools
  • __odlint.dm
  • __spacemandmm.dm
  • _build_dependencies.sh
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .tgs.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • dreamchecker.exe
  • LICENSE-AGPLv3.txt
  • LICENSE-CC-BY-NC-SA-3.0.txt
  • LICENSE-CC-BY-SA-3.0.txt
  • LICENSE-GPLv3.txt
  • mkdocs.yml
  • paradise.dme
  • prof.dll
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rustlibs_prod.dll
  • rustlibs.dll
  • SpacemanDMM.toml
  • TGS3.json