Skip to content

Repository files navigation

The DevOps Maturity Specification

DevOps MaturityWebsite

The DevOps Maturity specification is standardized to assess the maturity of DevOps practices. It is a set of criteria to help you measure and improve your DevOps maturity.

DevOps Maturity is a broad DevOps baseline assessment. It does not replace specialized supply-chain security standards like SLSA. See the SLSA mapping for where the two frameworks overlap.

How it compares

DevOps Maturity is a breadth-first, automatable baseline across the whole delivery lifecycle. Adjacent frameworks go deeper but narrower, or measure outcomes rather than practices — they complement it rather than compete with it.

FrameworkPrimary focusBest for
DevOps MaturityDevOps practices & controls in place (build, quality, security, supply chain, analysis, reporting)A fast, broad baseline + shareable badge for OSS and internal repos
DORA metricsDelivery outcomes (deploy frequency, lead time, MTTR, change-fail rate)Tracking delivery performance once practices exist
OpenSSF ScorecardOSS security health (repo-level heuristics)Hardening the security posture of a public repo
OpenSSF Best PracticesOSS best-practice badge (web SaaS, self-attested)Earning a recognized OSS badge
SLSASupply-chain integrity (provenance & attestation)Deep, verifiable supply-chain assurance

What makes it different: breadth beyond security; automatable end-to-end (YAML in, JSON/badge out, GitHub Action in CI); AI-powered auto-assessment from repo metadata; and CLI / self-hostable web UI that works on private repos with no SaaS lock-in.

See the full comparison and "when to use which" on the specification site.

Schema

The assessment file format is defined by a JSON Schema. Criteria accept both simple boolean values and structured objects with evidence, verification metadata, and rationale:

# Simple boolean — quick self-assessmentD101: trueD202: false# Structured — auditable evidenceD403:
status: trueevidence:
- type: workflowpath: .github/workflows/release.yml
- type: artifact-signaturetool: cosignverified_by: devops-maturity-actionverified_at: "2026-05-24T00:00:00Z"rationale: "Release workflow signs artifacts with Cosign keyless signing"

🎉 Show Your Support

If you find this useful, consider giving it a ⭐️ on GitHub! Your support helps others discover and adopt the spec.

🛡 Badges!

Let others know your project follows the DevOps Maturity specification. Add this badge to your repository README:

[![DevOps Maturity](https://img.shields.io/badge/DevOps%20Maturity-Specification-yellow)](https://devops-maturity.github.io/)

Additional Documents

🤝 Contributing

We welcome contributions from the community!
If you'd like to help improve the DevOps Maturity Specification — whether it's fixing a typo, improving the questions, or proposing a new maturity dimension — please check out our contributing guidelines.

No contribution is too small. Thank you for helping us grow! 💛

About

DevOps Maturity Specification

Topics

Resources

Code of conduct

Contributing

Stars

1 star

Watchers

1 watching

Forks

Releases

Sponsor this project

Used by

Contributors

Languages