Pakua SysManager 1.136.157

[1.136.157] - 2026-11-09
Ping, Bandwidth Monitor, Resource History and Settings Watchdog fit the default window again, and an empty state
inside a small card leaves out its icon.
Fixed
- Since 1.136.156 a page keeps the height its content needs and scrolls. At the default window four pages scrolled
only because of one thing in a card: Ping's and Bandwidth Monitor's charts asked for 200 and 160 px where the
window gave them 141 and 115, Resource History's charts for 180 and 120 and its temperature card's "No temperature
data" for 158 px in 95, and Settings Watchdog's "No changes detected" for 15 px more than its list had. An empty
state in a card beside or in place of a chart or a console, in Resource History, Bandwidth Monitor, Settings
Watchdog and every console, now leaves its icon out and keeps 12 px above and below instead of 24, and each chart's
minimum is the height the default window gives it: Ping's 136, Bandwidth Monitor's 104, Resource History's 160 and
92. Those four pages fit the default window, and on a smaller one keep their charts that tall and scroll.
- Quick Cleanup's and System Fixes' consoles and Settings Watchdog's list need no floor of their own any more, and App
Updates' console is 180 px again. Quick Cleanup still scrolls at the default window, by 69 px: the cards above its
console take 690 of the page's 781.
- Two comparisons of the scroll offset in the shell's page host tested doubles for exact equality, which code
scanning flagged. One now asks which is smaller, as a clamp only ever lowers the offset, and the other ignores a
move of less than a hundredth of a pixel.
- Tests pin the compact empty state, with its icon left out and 12 px above and below, and that a state with no icon
shows none, full or compact.
Verify the download
Get-FileHash .\SysManager-v1.136.157.exe -Algorithm SHA256
Expected SHA256: 9A52F5C8A92B62D5E7F6F631510FF4C4B533625DD14AAFDC7A936253086A77BC
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.157.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.157.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.