Pearipherals v1.2.0 — UNSIGNED prerelease
Pre-releaseWarning
UNSIGNED PRERELEASE — NOT AN OFFICIAL SIGNED RELEASE
Pearipherals-1.2.0-unsigned.exe has no Authenticode signature. Windows cannot verify its publisher identity. Microsoft Defender SmartScreen may warn, and Smart App Control may block it; Smart App Control has no per-app bypass. Do not disable system-wide Windows security protections to run this build.
Download
Download Pearipherals-1.2.0-unsigned.exe below. The separately attached warning and SHA-256 file repeat the trust status and expected checksum.
This prerelease exists so people can use and evaluate the current open-source version while Pearipherals establishes the public adoption required to reapply for free trusted signing.
Source and build provenance
- Source commit:
25c8dc465a502bd842313507eb1a4fe7e70616a5 - Tag:
v1.2.0-unsigned(must resolve to the source commit above) - GitHub Actions run: Build and sign Windows release #32294606204
- Runner: GitHub-hosted
windows-2022 - Build environment: Python 3.11.9, PyInstaller 6.21.0, complete hash-locked dependencies, no dependency cache
- Signing steps: deliberately skipped because
submit_for_signing=false; no SignPath credential or signature was used
Verification
- Complete automated suite: 83 tests passed
- Python byte compilation: passed
- PE format: x64 PE32+ Windows GUI executable
- Product name:
Pearipherals - Product version / file version:
1.2.0 - Original filename metadata:
Pearipherals.exe Get-AuthenticodeSignature:NotSigned- PE certificate table: empty (
VirtualAddress=0,Size=0) - Microsoft Defender custom scan on the downloaded artifact: no threats found
- Published EXE size:
19,425,000bytes - SHA-256:
253cd57c0c66c8e7673e372b27df91ecdca1e3605541ea4a2497041b74e259cd Pearipherals-1.2.0-unsigned.exe
The checksum detects a file mismatch or corruption only. It does not authenticate the publisher, establish that the executable is safe, or substitute for a digital signature. A clean antivirus scan is also not a guarantee of safety.
What changed since v1.1
- Separate Magic Keyboard and Magic Trackpad battery levels in the tray
- Safer battery polling and sleep/wake recovery
- Hardened keyboard-hook, pointer-suppression, shutdown, and retry behavior
- More reliable three-finger gesture tracking across contact churn, lifts, disconnects, and stale reports
- Fixed padding contact ID
65535falsely turning two-finger scrolling into a three-finger gesture - Safer, durable backup and restoration of Windows touchpad settings
- Corrupt-configuration preservation and recovery handling
- Windows product/version metadata and a verified release-build pipeline
The v1.2.0 feature set and the two-finger padding-contact fix have been physically accepted on the maintainer's Windows 11 setup. This downloadable artifact was rebuilt from the exact source commit above by GitHub Actions and passed the automated gates listed here.
Requirements
- Windows 10 or Windows 11
- Apple Magic Keyboard and/or Magic Trackpad 2 over Bluetooth
- For Magic Trackpad pointer movement and two-finger scrolling: the free, signed mac-precision-touchpad driver
Signing status
Pearipherals applied to SignPath Foundation for free open-source signing. The application was not accepted because the project is new and does not yet have enough established public usage. This was an adoption/reputation decision, not a malware finding. The project plans to reapply after more people use it.
See the code signing policy, privacy policy, and uninstall instructions.
Pearipherals is not affiliated with Apple Inc.