lesspass/lesspass: technical due diligence, read from its repository

The median source file here is 33 lines. 1 file exceed 1,000 lines, the largest being 1,441. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

76 product files are in the new language and 46 are still in the old one, 78 months after the first new file appeared. The new language's share of the lines rose from 0% to 57%, and moved 0 percentage points in the last year. Two languages for one job doubles what an engineer has to know, and the unmoved half is usually what nobody wants to touch. Ask whether finishing it is planned, and what it costs.

The newest release, 9.1.9, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.

11 of 1,510 locked dependencies match 24 published advisories in OSV, 9 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

The root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.

The newest was published on 2026-03-09. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version.