Pakua SysManager 1.136.142

[1.136.142] - 2026-11-06
The words on the status chips are easy to read on every theme now, where "Not recognised", "Unsigned", "Known app"
and "Verified" were faint on most of them.
Fixed
- The grey "Not recognised" chip on Process Manager (since 1.59.0) and "Unsigned" on Startup Manager (since 1.85.0),
which between them are most rows, used one fixed grey on every theme, an old copy of the default theme's muted text.
Against its own tint it measured 2.73 to 3.99:1 at the top of a card on all twelve themes, where small text needs
4.5. Each mode has its own neutral grey now, the one the verbose output lines use, on a tint of itself, and "Not
rated" on Services and Windows Features takes the same pair.
- On the light themes the green "Known app", "Verified" and "Safe" chips measured 3.66 to 4.24:1, and the blue
"Windows" chip 4.37 on Soft Blossom and Lavender (since 1.52.23). Both texts are a step darker on the light themes
now, the shades the light themes' green and blue already used elsewhere.
- A test reads every chip's words against its tint over the card, and over the top of the card's sheen, on all twelve
built-in themes. Before, the light success text was checked against white only and the grey against nothing.
Verify the download
Get-FileHash .\SysManager-v1.136.142.exe -Algorithm SHA256
Expected SHA256: 8B4A845383229E017F7A3A68A8AB8C61FEF994B6081EB1C3CA9624D2E5304781
This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use it. Full
privacy policy.
Verify where this binary came from
This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:
gh attestation verify .\SysManager-v1.136.142.exe --repo laurentiu021/SystemManager
That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.136.142.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.