Sækja SysManager 1.136.130

[1.136.130] - 2026-11-06
The log now says how long SysManager took to show its window, and every release records it.
Added
- Nothing measured how long SysManager takes to start. The log now has a line for the window's first frame: how
many milliseconds after the process started it was drawn, and the priority the process ran at. The release's
check of the published exe writes that figure to its summary, with how much memory the start used, so a change
that slows the start shows in the release that ships it. A release is not held back for it, and one whose log
has no such line gets a warning.
Verify the download
Get-FileHash .\SysManager-v1.136.130.exe -Algorithm SHA256
Expected SHA256: 23CDD3B979999E25BD363B5891F5BA15AEE672EE1DC7ACE788214BC612B94F54
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.130.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.130.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.