Skip to content
DevUtils Online

DevOps

lens vs wtf

wtf leads by 17.5 · decisive

A

lens

76.2

23,248 stars · MIT

B · leads

wtf

93.7

17,154 stars · MPL-2.0

lens versus wtf is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lens is written mainly in an unspecified language; wtf is written mainly in Go. The composite score is 76.2 for lens and 93.7 for wtf.

lens has 23,248 GitHub stars to wtf's 17,154, a gap of 6,094 (1.36×). Forks are 1,466 for lens and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 93.

Push history: lens was last pushed on 11 February 2025 (644 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 1,165 for lens (0.050 per star) and 107 for wtf (0.006 per star). Issue-health scores are 52 and 84; activity scores are 16 and 100.

lens 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for lens and 78 for wtf. This is a procurement signal, not legal advice.

In DevOps, both lens (23,248 stars) and wtf (17,154 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: lens is open source, wtf is open source.

The lead is split. lens is furthest ahead on license flexibility (96 to 78), while wtf is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.

wtf finishes ahead at 93.7 against lens at 76.2, a 17.5 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.

lens versus wtf metrics
Signal lens wtf
GitHub stars 23,248 17,154
Forks 1,466 866
Open issues 1,165 107
Adoption 100 97
Activity 16 100
Community 100 93
Issue health 52 84
License 96 78
Self-hosting 100 100
Composite 76.2 93.7

Questions this page answers

Which has more GitHub stars, lens or wtf?

lens has more GitHub stars: 23,248 versus 17,154 for wtf. The gap is 6,094 stars.

Which was updated more recently, lens or wtf?

wtf was pushed more recently: 14 November 2026 versus 11 February 2025 for lens. That is 641 days apart.

Can I self-host both lens and wtf?

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

Which license is easier to embed in a commercial product, lens or wtf?

lens 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the lens vs wtf score?

wtf scores 93.7 and lens scores 76.2. This page calls that a decisive lead for wtf.

Related comparisons