nasa/cfs

0

/ 100

Documentation88
Engineering29
Health68
C1,375Apache-2.01d ago
Grade a repo

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

The Core Flight System (cFS)

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