Review criteria
Every entry is a dated assessment of a specific public artifact.
Stages
Public availability, not severity- Public release
- A usable artifact or source release exists within the documented scope.
- Public PoC
- A proof of concept is available. Capability may stop at a crash or a limited read/write.
- Private demonstration
- A result is shown, with implementation or reproduction still unavailable.
- Release announced
- The original researcher has stated a publication plan. The artifact is pending.
- Pending evidence
- A material gap keeps the item out of the main register.
The four bars show how much of a development is publicly available. Capability is assessed separately in each entry.
What qualifies
A material source release, a substantive disclosure, a useful reproduction, or an original researcher’s specific announcement or demonstration. Each must change the understanding of a capability, support range, delivery path, patch, or release.
For source repositories, inspect the actual code at a frozen revision. Trace the path from attacker input to the reported effect. Check build requirements, supplied logs, controls, and attribution. A convincing README with a placeholder implementation does not qualify. Reposts and copied evidence do not provide independent confirmation.
What the claim must establish
- The exact device and build
- The process that handles the input
- The address and value the input can influence
- The effect that survives the corruption
- The protections and chain stages still needed
A crash is a crash. A bounded file read is a bounded file read. Kernel memory access does not establish a code-signing bypass, persistence, or a complete jailbreak. Runtime claims remain attributed to their source until independently reproduced.
How the loop works
- 08:00 & 20:00 Pacific. A research pass samples original X posts, accessible Discord research discussions, and repository changes. It follows leads to public primary sources and updates qualifying records through a branch and pull request.
- 03:23 & 15:23 UTC. A GitHub Actions check compares watched commits and published releases with reviewed baselines. Changes open or update a review issue. This check does not judge new capabilities.
- Access. The research pass needs the local computer, the app, and signed-in source sessions. When a source is inaccessible, its check is marked blocked. No full-platform coverage is implied. Private discussions and direct messages are never published.
Technical terms
- PoC
- Proof of concept: an artifact that reproduces a specific behavior.
- Kernel read/write
- The ability to read or change kernel memory. Address, value, and memory-region restrictions still matter.
- SPTM / TXM
- Apple’s Secure Page Table Monitor and Trusted Execution Monitor protect memory mappings and code policy beyond ordinary kernel authority.
- PAC
- Pointer authentication: checks that help protect code pointers and return addresses.
- MIE
- Memory Integrity Enforcement: Apple’s memory allocators, tagging, and related protections on supported hardware.
- Tethered boot
- A boot workflow that requires an attached computer each time the device starts.