nasa/cfs
Grade a repo

0

/ 100

GradeF

Strong community interest, but tests, CI, or docs need work.

Higher than 40% of 5,156 graded repos

The Core Flight System (cFS)

Documentation88
Engineering29
Health68
C1,375Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (81).

See your top fixes
Now
F
55
Potential
B
81

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

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 Apache-2.0.

Engineering

29

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

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-cfs-multitarget.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 361
    Forks
  • 19
    Releaseslatest 4y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,375
    Watchers

Responsiveness

  • 8h
    Median issue response
  • 5d 19h
    Median PR merge time
  • 91
    Open issues
Repository files41 root entries
  • .github
    Good: CI is configured (.github/workflows/build-cfs-multitarget.yml).
    Good: Issue or PR templates present.
  • actions
  • apps
  • libs
  • sample_defs
  • tools
  • .clang-format
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .lgtm.yml
  • cfe
  • cFS_Apps_Corporate_CLA.pdf
  • cFS_Apps_Individual_CLA.pdf
  • cFS_Framework_Corporate_CLA.pdf
  • cFS_Framework_Individual_CLA.pdf
  • CITATION.cff
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • custom-rules.mk
  • distbuild.mk
  • EDS_Integration_Guide.md
  • edslib-test.mk
  • goal-configs.mk
  • INTEGRATION.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • local-test.mk
  • Makefile
  • native_eds-test.mk
  • native_std-test.mk
  • osal
  • osal-test.mk
  • pc686_rtems5-test.mk
  • psp
  • qemu_yocto_linux-test.mk
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • simple_defs
  • simple.mk
  • target-configs.mk
  • target-rules.mk
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/nasa/cfs)](https://www.repo-grade.com/report/nasa/cfs)

More graded C repos