v1.36.0 - The screencap command in any terminal

The screencap command in any terminal

• The Windows setup adds the program folder to the PATH, so screencap works in any new PowerShell, Command Prompt, or Windows Terminal window. An install for all users adds it to the system PATH; an install for you only adds it to your own PATH. It is ticked by default on the Options page, works in silent installs, and is never added twice. Untick it, or use /MERGETASKS="!addtopath", to leave the PATH alone. Uninstalling takes it out again.
• winget lists the screencap command for this package.

New

• Every release file now has a build provenance record: gh attestation verify <file> --repo ILikeHostingServices/Screencap-Documentation-Tool proves it was built by this repository's GitHub Actions workflow and not changed afterwards.
• Each release lists the Windows app's components in a CycloneDX SBOM (*-windows-sbom.cdx.json), for vulnerability scanners and procurement reviews.
• ScreenCap Docs for IT and Security Teams: what the app does on a PC, its network use, files, administrator settings, and how to verify a download.
• CodeQL and the OpenSSF Scorecard check the repository on every change.
• CONTRIBUTING.md explains how to report bugs, propose a change, and what a pull request must include.

Improved

• The README leads with the Windows setup as the main way to install. The PowerShell install command is in its own section for power users and developers.

Fixed

• A recording failed to process when automatic blurring found text in the last pixel row or column of the screen, or when a blur box was only a few pixels wide: FFmpeg refused the box and the whole recording was marked Failed. Blur boxes are now kept inside the screen and are at least 8 pixels on each side, so they always render and still cover the text.