Take part
Report a test
Test reports are what give a project its status. A project becomes community-verified when three people who don't maintain it report its newest release working or partly working, and reported-broken when at least two of them report it broken and outnumber the working reports. Your report counts the same as anyone else's.
Steps
- Find the project in the catalog. At the bottom of its page there is a template filled in with its id and newest release.
- Fork openkext/registry and add
kexts/<id>/reports/<your-github-login>/<name>.toml. The folder must be your own login. The file name is up to you, for example1.0.0-25g332.toml. - Fill in the result, your macOS version and build (
sw_vers), and your hardware. List the features you tried under[features]. - Open a pull request with that one file. The bot checks it and merges it if it passes.
Faster: let the script fill it in
On the Mac you tested, from a clone of the registry:
python3 tools/make_report.py <id> <version> works --device 8086:2725 \
--feature wifi=works --notes "what you tested" --login <your-github-login> --write
It fills in your macOS version and build, CPU and SMBIOS model (nothing else: no serial numbers or MAC addresses), saves the file in your folder and checks it. An AI coding agent can run it for you; AGENTS.md tells it how. Read the file before you send it.
What makes a useful report
- Say what you tested and what you didn't. "Wi-Fi works, sleep untested" is more useful than "works".
- Use
partialwhen the main function works but something is missing or unreliable, and explain it innotes. - Use
brokenwhen the driver doesn't load, panics, or its main function doesn't work. Include the macOS build and, if you can, the log line or panic message. - Your newest report for a release is the one that counts. To change your result, add a new file; don't edit the old one.
Reports are public and tied to your GitHub account. Don't include serial numbers, MAC addresses, network names or anything else personal. Reports that are fake or part of a coordinated campaign can be removed by a maintainer, with a note in the pull request that removes them.
Test reports
One file per test: kexts/<id>/reports/<your-github-login>/<name>.toml. The name is up to you (lowercase letters, digits, ., _, -), for example 1.0.0-25g332.toml.
kext = "demo-wifi"
version = "1.0.0" # a release listed in kext.toml
asset = "DemoWiFi-1.0.0.zip" # optional: which asset you installed
result = "works" # works | partial | broken
date = 2026-11-15
notes = "What you tested, what failed. Up to 2000 characters."
[macos]
version = "26.7.2"
build = "25G332" # sw_vers -buildVersion
[hardware]
cpu = "Intel Core i5-8500"
smbios = "iMac19,1"
bootloader = "OpenCore 1.0.8" # optional
board = "Gigabyte B360M" # optional
device_ids = ["8086:2725"] # optional: the device the project drives
[features] # optional: name = works | partial | broken | untested
wifi = "works"
airdrop-send = "partial"
Don't include serial numbers, MAC addresses, network names or anything else personal. Reports are public.
Edit this page on GitHub. Something wrong or unclear? Open an issue or a pull request.