You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -78,3 +64,24 @@ You can used [devops-maturity](https://github.com/devops-maturity/devops-maturit
78
64
### What is the difference between OpenSSF Best Practices and DevOps Maturity?
79
65
80
66
[OpenSSF Best Practices](https://www.bestpractices.dev/) targets open source projects across the entire software development lifecycle, while DevOps Maturity focuses specifically on DevOps practices applicable to both open source and internal enterprise projects. DevOps Maturity provides both a web UI and a CLI for automatic maturity scoring. In contrast, OpenSSF Best Practices only offers a web-based SaaS and does not support internal deployment.
67
+
68
+
[^1]: Supports builds from any specific branch, not just the `main` branch.
69
+
[^2]: Supports building pull requests (PRs), not limited to direct pushes to branches.
70
+
[^3]: Supports building in clean environments, such as containers or virtual machines (VMs).
71
+
[^4]: Supports unit testing, including unit or component-level tests.
72
+
[^5]: Supports functional testing, such as integration or end-to-end (E2E) tests.
73
+
[^6]: Supports performance testing, including load, stress, or throughput testing.
74
+
[^7]: Supports measuring code coverage, including line, branch, or function coverage.
75
+
[^8]: Supports accessibility testing for standards compliance, such as WCAG.
76
+
[^9]: Supports security scanning, including SAST (Static Application Security Testing) and DAST (Dynamic Application Security Testing).
77
+
[^10]: Supports license scanning using tools like SPDX, FOSSology, or license-checkers.
78
+
[^11]: Provides a documented build process, including build steps, manifests, or reproducibility details.
79
+
[^12]: Supports CI/CD workflows defined as code, such as pipeline-as-code or infrastructure-as-code.
80
+
[^13]: Supports artifact signing (e.g., with PGP or GPG) to ensure authenticity and integrity.
81
+
[^14]: Supports dependency pinning or version locking to ensure reproducible builds.
82
+
[^15]: Supports static code analysis tools such as SonarQube, Polaris, or similar.
83
+
[^16]: Supports dynamic analysis, including runtime behavior analysis or fuzz testing.
84
+
[^17]: Supports code linting using tools like ESLint, Prettier, or pre-commit hooks.
85
+
[^18]: Supports notification systems such as email or Slack alerts.
86
+
[^19]: Supports attaching detailed reports to builds, such as test results or coverage metrics.
0 commit comments