A · level
devops-exercises
71.9
86,874 stars · license n/a
DevOps
Too close to call · 71.9 to 72.4
A · level
71.9
86,874 stars · license n/a
B · level
72.4
7,064 stars · MIT
devops-exercises versus tfsec is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. devops-exercises is written mainly in Python; tfsec is written mainly in Go. The composite score is 71.9 for devops-exercises and 72.4 for tfsec.
devops-exercises has 86,874 GitHub stars to tfsec's 7,064, a gap of 79,810 (12.30×). Forks are 20,674 for devops-exercises and 560 for tfsec. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 64.
Push history: devops-exercises was last pushed on 27 December 2025 (325 days ago), and tfsec was last pushed on 25 March 2026 (237 days ago). Open issues stand at 59 for devops-exercises (0.001 per star) and 19 for tfsec (0.003 per star). Issue-health scores are 96 and 96; activity scores are 36 and 36.
devops-exercises is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. tfsec is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for devops-exercises and 96 for tfsec. This is a procurement signal, not legal advice.
Only tfsec is marked self-hostable here (7,064 stars, deploy score 100). devops-exercises is not (86,874 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: devops-exercises is unpriced in this catalog, tfsec is open source.
The lead is split. devops-exercises is furthest ahead on fork community (100 to 64), while tfsec is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Composite score: devops-exercises 71.9, tfsec 72.4. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | devops-exercises | tfsec |
|---|---|---|
| GitHub stars | 86,874 | 7,064 |
| Forks | 20,674 | 560 |
| Open issues | 59 | 19 |
| Adoption | 100 | 78 |
| Activity | 36 | 36 |
| Community | 100 | 64 |
| Issue health | 96 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 71.9 | 72.4 |
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
Tfsec is now part of Trivy
devops-exercises has more GitHub stars: 86,874 versus 7,064 for tfsec. The gap is 79,810 stars.
tfsec was pushed more recently: 25 March 2026 versus 27 December 2025 for devops-exercises. That is 88 days apart.
Only tfsec is marked self-hostable. devops-exercises is not.
devops-exercises is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. tfsec is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. devops-exercises scores 71.9 and tfsec scores 72.4.