Skip to content
DevUtils Online

DevOps

90DaysOfDevOps vs task

task leads by 20.8 · decisive

B · leads

task

92.7

16,362 stars · MIT

90DaysOfDevOps versus task is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. 90DaysOfDevOps is written mainly in Shell; task is written mainly in Go. The composite score is 71.9 for 90DaysOfDevOps and 92.7 for task.

90DaysOfDevOps has 30,916 GitHub stars to task's 16,362, a gap of 14,554 (1.89×). Forks are 6,812 for 90DaysOfDevOps and 945 for task. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 78.

Push history: 90DaysOfDevOps was last pushed on 24 June 2026 (146 days ago), and task was last pushed on 17 November 2026 (0 days ago). Open issues stand at 12 for 90DaysOfDevOps (0.000 per star) and 195 for task (0.012 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.

90DaysOfDevOps 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. task 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 90DaysOfDevOps and 96 for task. This is a procurement signal, not legal advice.

Only task is marked self-hostable here (16,362 stars, deploy score 100). 90DaysOfDevOps is not (30,916 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: 90DaysOfDevOps is unpriced in this catalog, task is open source.

The lead is split. 90DaysOfDevOps is furthest ahead on fork community (100 to 78), while task is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

task finishes ahead at 92.7 against 90DaysOfDevOps at 71.9, a 20.8 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

90DaysOfDevOps versus task metrics
Signal 90DaysOfDevOps task
GitHub stars 30,916 16,362
Forks 6,812 945
Open issues 12 195
Adoption 100 94
Activity 36 100
Community 100 78
Issue health 96 84
License 30 96
Self-hosting 35 100
Composite 71.9 92.7

90DaysOfDevOps

This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, 90DaysOfDevOps or task?

90DaysOfDevOps has more GitHub stars: 30,916 versus 16,362 for task. The gap is 14,554 stars.

Which was updated more recently, 90DaysOfDevOps or task?

task was pushed more recently: 17 November 2026 versus 24 June 2026 for 90DaysOfDevOps. That is 146 days apart.

Can I self-host both 90DaysOfDevOps and task?

Only task is marked self-hostable. 90DaysOfDevOps is not.

Which license is easier to embed in a commercial product, 90DaysOfDevOps or task?

90DaysOfDevOps 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. task 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.

Who wins the 90DaysOfDevOps vs task score?

task scores 92.7 and 90DaysOfDevOps scores 71.9. This page calls that a decisive lead for task.

Related comparisons