Skip to content

Security: reesoousa/boringCode

Security

SECURITY.md

Security Policy

Supported Versions

Only the latest release (and the main branch) receives security fixes. Beta builds on the dev branch are development snapshots.

Reporting a Vulnerability

The Bored Team and community take security bugs in Boring Notch seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.

To report a security issue, please use the GitHub Security Advisory "Report a Vulnerability" tab.

The Bored Team will send a response indicating the next steps in handling your report. After the initial reply to your report, we will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Report security bugs in third-party dependencies to the person or team maintaining the package or dependency.

Security Notes for Users and Contributors

Private / undocumented APIs

Boring Notch uses private macOS APIs and frameworks to deliver features not possible with the public SDK: the notch window lives in a private SkyLight space (boringNotch/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. This usage is also why the app is distributed outside the App Store.

XPC helper privilege model

The app is sandboxed (see boringNotch/boringNotch.entitlements), but its bundled XPC service BoringNotchXPCHelper (BoringNotchXPCHelper/BoringNotchXPCHelper.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/BoringNotchXPCHelperProtocol.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 binaries

mediaremote-adapter/ contains vendored binaries built from ungive/mediaremote-adapter; see its README for the pinned version, rebuild instructions, and verification notes.

There aren't any published security advisories