pickfit

BrowseOther

Progressive

Open-source TODO list and progress tracker with nested subtasks and weights.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 38 known high or critical vulnerabilities (52 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:zip 4.6.1 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • npm:tar 7.5.1 node-tar: Decompression/parse DoS via unlimited input (GHSA-23hp-3jrh-7fpw, critical, fixed in 7.5.19)
See 8 more

42 more findings not listed here.

Linux x86_64

You need first

  • At least 2 GB of RAM
  1. add flathub remote for user

    flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
  2. install progressive via flatpak

    flatpak install --user -y flathub io.github.h8moss.progressive

Start Progressive from your applications menu, or run flatpak run io.github.h8moss.progressive in a terminal.

What it does

  • Organize tasks into nested subtasks
    Not tested
  • Give tasks weights
    Not tested
  • Treat weights as different units
    Not tested
  • Change the look with custom themes
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Opens to its setup screen
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • create tasklist with subtasks and progress
  • see overall accomplished progress

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

It opens to its first-run screen

  • Replayed from scratch
  • Checked on 1 Nov 2026

When pickfit opened it, its first-run (setup) screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.