Notch Pocket development and security fixes target pocket. There are no
independent binary releases available yet; inherited upstream releases are not
Notch Pocket releases.
Notch Pocket is maintained by @jdylanmc, independently of The Bored Team. Please disclose security findings responsibly.
If enabled, use the repository's GitHub Security Advisory "Report a Vulnerability" tab. If private reporting is unavailable, contact the maintainer through their GitHub profile to arrange a private channel; do not post sensitive details in public issues.
The maintainer may request additional information to investigate a report.
Report security bugs in third-party dependencies to the person or team maintaining the package or dependency.
Notch Pocket uses private macOS APIs and frameworks to deliver features not
possible with the public SDK: the notch window lives in a private SkyLight
space (notchPocket/private/), media metadata comes from the private
MediaRemote.framework (via the vendored
MediaRemoteAdapter), and OSD display control
uses private DisplayServices/brightness symbols. These interfaces are
undocumented, may change with any macOS update, and the app may lose features
without warning when they do. These APIs also constrain any future distribution;
local builds are not App Store or notarized releases.
The app is sandboxed (see notchPocket/notchPocket.entitlements), but its
bundled XPC service notchPocketXPCHelper
(notchPocketXPCHelper/notchPocketXPCHelper.entitlements) is not —
sandboxed processes cannot drive the Accessibility API on other apps or load
private frameworks the app needs for notification/brightness features. The
helper is intentionally minimal: it exposes a narrow typed protocol
(Shared/NotchPocketXPCHelperProtocol.swift) and accepts connections only
from the bundled app. When auditing, treat the helper as the highest-trust
component in the repo: its attack surface is the XPC protocol plus the
Accessibility API.
mediaremote-adapter/ contains vendored binaries built from
ungive/mediaremote-adapter;
see its README for the pinned version,
rebuild instructions, and verification notes.