mitre/saf
Grade a repo

84

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and a contributing guide.

Top 24% of 5,156 graded repos

The MITRE Security Automation Framework (SAF) Command Line Interface (CLI) brings together applications, techniques, libraries, and tools developed by MITRE and the security community to streamline security automation for systems and DevOps pipelines

Documentation70
Engineering88
Health97
HTML196Other3d ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Issue and PR templates6pt

    Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

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

70

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

88

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt100

Test files detected (test).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Project health

97

Dependency manifest6pt90

Dependency manifest found (package.json).

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

  • 272 / 1163
    Commits (30d / 90d)
  • 45
    Forks
  • 104
    Releaseslatest 4y ago

Community

  • 37% - Weak
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 196
    Watchers

Responsiveness

  • 4d 17h
    Median issue response
  • <1h
    Median PR merge time
  • 159
    Open issues
Repository files36 root entries
  • .github
    Good: CI is configured (.github/workflows/build-macos.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
  • .vscode
  • bin
  • docs
  • src
  • test
    Good: Test files detected (test).
  • _config.yml
  • .deepsource.toml
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env-example
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • CNAME
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.js
  • LICENSE.md
    Good: Licensed under Other.
  • oclif-theme.json
  • pack-hdf-converters.bat
  • pack-hdf-converters.sh
  • pack-heimdall-lite.bat
  • pack-heimdall-lite.sh
  • pack-inspec-objects.bat
  • pack-inspec-objects.sh
  • pack-inspecjs.bat
  • pack-inspecjs.sh
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • release-prep.ps1
  • release-prep.sh
  • saf-cli.code-workspace
  • saf.spec
  • tsconfig.json
  • VERSION
  • vitest.config.ts
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/mitre/saf)](https://www.repo-grade.com/report/mitre/saf)

More graded HTML repos