0

/ 100

GradeB

Solid foundation. Invest in docs and CI to grow from here.

Top 28% of 5,156 graded repos

The Atmospheric Radiative Transfer Simulator

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

90

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt93

README is present.

License6pt100

Licensed under Other.

Engineering

69

Reproducibility6pt10

No dependency lockfile found (−70 pts).

Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (3rdparty/invlib/test).

Linting and formatting5pt100

Linter or formatter configured (.flake8).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (3rdparty/shtns/setup.py).

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)
  • 36
    Forks
  • 20
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 2d 23h
    Median issue response
  • 2h
    Median PR merge time
  • 17
    Open issues
Repository files34 root entries
  • .github
    Good: CI is configured (.github/workflows/build-test.yml).
    Good: Issue or PR templates present.
  • 3rdparty
    Good: Licensed under Other.
    Good: Test files detected (3rdparty/invlib/test).
    Good: Dependency manifest found (3rdparty/shtns/setup.py).
  • actions
    Good: Environment pinned via actions/pypi/Dockerfile.
  • cmake
  • doc
  • examples
  • python
  • src
  • testdata
  • tests
  • tools
  • .blameignorerevs
  • .clang-format
  • .clang-tidy
  • .clangd
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitignore
    Good: .gitignore present.
  • AUTHORS
  • CHANGES-2.2
  • CHANGES-2.4
  • CMakeLists.txt
  • CMakePresets.json
  • config.h.cmake
  • CONTRIBUTING.md
    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.
  • environment-dev-linux-clang.yml
  • environment-dev-linux.yml
  • environment-dev-mac.yml
  • environment-dev-win.yml
  • GITHUB-INTRO.md
  • KNOWN_ISSUES
  • LICENSE.txt
  • NOTES-vZ.txt
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
  • TODO
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/atmtools/arts)](https://www.repo-grade.com/report/atmtools/arts)

More graded C++ repos