spiffe/spire
Grade a repo

0

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 10% of 5,156 graded repos

The SPIFFE Runtime Environment

Documentation87
Engineering92
Health100
Go2,413Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

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

87

Contributing guide5pt72

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

92

CI/CD14pt72

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

Tests18pt100

Test files detected (cmd/spire-agent/cli/api/api_posix_test.go).

Linting and formatting5pt100

Formatting enforced (.golangci.yml).

Reproducibility6pt100

Lockfile present (go.sum). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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)
  • 625
    Forks
  • 138
    Releaseslatest 7y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,413
    Watchers

Responsiveness

  • 16d 1h
    Median issue response
  • 2h
    Median PR merge time
  • 128
    Open issues
Repository files37 root entries
  • .data
  • .github
    Good: CI is configured (.github/workflows/nightly_build.yaml).
    Good: Dependabot covers 2 ecosystems (gomod, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • cmd
    Good: Test files detected (cmd/spire-agent/cli/api/api_posix_test.go).
  • conf
  • doc
  • examples
  • pkg
  • proto
  • release
  • script
  • support
  • test
  • .dockerignore
  • .envrc.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .go-version
  • .golangci.yml
    Good: Formatting enforced (.golangci.yml).
  • .markdownlint.yaml
  • .spire-tool-versions
  • ADOPTERS.md
  • CHANGELOG.md
  • CODE-OF-CONDUCT.md
  • CODEOWNERS
  • 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.
    Good: Contributing guide describes code style expectations.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.dev
  • Dockerfile.windows
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS.md
  • Makefile
  • 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.
  • RELEASING.md
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.
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/spiffe/spire)](https://www.repo-grade.com/report/spiffe/spire)

More graded Go repos