Skip to content
DevUtils Online

DevOps

act vs Yearning

act leads by 22.1 · decisive

A · leads

act

99.1

72,721 stars · MIT

B

Yearning

77.0

8,981 stars · AGPL-3.0

act versus Yearning is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 99.1 for act and 77.0 for Yearning.

act has 72,721 GitHub stars to Yearning's 8,981, a gap of 63,740 (8.10×). Forks are 2,126 for act and 2,032 for Yearning. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 99.

Push history: act was last pushed on 16 November 2026 (1 day ago), and Yearning was last pushed on 24 August 2026 (85 days ago). Open issues stand at 318 for act (0.004 per star) and 164 for Yearning (0.018 per star). Issue-health scores are 96 and 84; activity scores are 100 and 58.

act 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. Yearning is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for act and 52 for Yearning. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and Yearning (8,981 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: act is open source, Yearning is open source.

act is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

act finishes ahead at 99.1 against Yearning at 77.0, a 22.1 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.

act versus Yearning metrics
Signal act Yearning
GitHub stars 72,721 8,981
Forks 2,126 2,032
Open issues 318 164
Adoption 100 81
Activity 100 58
Community 100 99
Issue health 96 84
License 96 52
Self-hosting 100 100
Composite 99.1 77.0

Questions this page answers

Which has more GitHub stars, act or Yearning?

act has more GitHub stars: 72,721 versus 8,981 for Yearning. The gap is 63,740 stars.

Which was updated more recently, act or Yearning?

act was pushed more recently: 16 November 2026 versus 24 August 2026 for Yearning. That is 84 days apart.

Can I self-host both act and Yearning?

Yes. This catalog marks both act and Yearning as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, act or Yearning?

act 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. Yearning is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the act vs Yearning score?

act scores 99.1 and Yearning scores 77.0. This page calls that a decisive lead for act.

Related comparisons