sxs-collaboration/spectre

0

/ 100

Documentation95
Engineering85
Health88
C++191Other1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

SpECTRE is a code for multi-scale, multi-physics problems in astrophysics and gravitational physics.

Documentation

95

Contributing guide5pt84

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

85

Reproducibility6pt70

Lockfile present (support/Python/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (external/libsharp/python/libsharp/tests).

CI/CD14pt85

CI is configured (.github/workflows/BuildDockerContainer.yaml).

Linting and formatting5pt100

Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

88

Dependency manifest6pt62

Dependency manifest found (pyproject.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)
  • 218
    Forks
  • 57
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 2d 15h
    Median issue response
  • 5h
    Median PR merge time
  • 622
    Open issues
Repository files26 root entries
  • .claude
  • .codex
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/BuildDockerContainer.yaml).
    Good: Issue or PR templates present.
  • .skills
  • cmake
  • containers
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Code of conduct present.
  • external
    Good: Test files detected (external/libsharp/python/libsharp/tests).
  • src
  • support
    Good: Lockfile present (support/Python/requirements.txt). Installs are reproducible.
  • tests
  • tools
  • .clang-format
  • .clang-tidy
  • .codecov.yaml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • citation.bib
  • CITATION.cff
  • CMakeLists.txt
  • LICENSE.txt
    Good: Licensed under Other.
  • Metadata.yaml
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • setup.cfg