Borehole · Project · free tier
microsoft/powertoys
Free reading: not for reliance
c512e06 · 9,696 commits · 8,999 files
Read 2026-10-04

microsoft/powertoys: technical due diligence, read from its repository

What Borehole read in microsoft/powertoys's code and history at c512e06: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenanceadequate
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturityadequate
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • AGENTS.md:8: states a policy on AI-generated contributions

Architecture & Codebase — including AI provenance

adequate
01.6

src/modules/ZoomIt/ZoomIt/PanoramaCapture.cpp is 18,049 lines, 322× this codebase's median file

adequate

The median source file here is 56 lines. 67 files exceed 1,000 lines, the largest being 18,049. 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.

01.42

1 model weight file committed directly to git

adequate

1 model weight files are stored in git itself, not in LFS, DVC or a model hub. Every clone carries them, the history keeps every version for good, and nothing records which run or data produced them.

Engineering Process & SDLC Maturity

adequate
02.24

5% of recent commits change more than 2,000 lines

adequate

106 of 2022 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.

Evidence
106 commits over 2,000 lines

Product & Engineering Maturity

adequate
04.19

15% of bug fixes add or change a test

adequate

Of 593 fixes in the last 24 months, 86 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
86 of 593
04.38

5 files still carry code deprecated more than two years ago

adequate

5 files were marked deprecated over two years ago and still are, the oldest since Apr 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v0.100.2, is not on the branch this survey read; the newest release on it is v0.98.1. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v0.100.2

Security & Reliability Posture

strong
05.65

1 advisory against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-06-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: its version is only known to be at least 0.98.1. Answer lives in: the release you run, set against each fixed version.

Evidence
2026-06-09: CVE-2026-42902 (high): Improper authorization in Microsoft PowerToys allows an authorized attacker to elevate privileges locally.

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on microsoft/powertoys: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.