Contributions are welcome and genuinely help the project grow. There are two main ways to help: testing and code.
Security report? Please don't file it as a normal issue or PR. HTID is biometric authentication, so it is a security matter. Use the security page.
Testing
Testing a sensor that is in development is the best way to make sure new code ships without bugs or security issues. Testers are heavily welcomed.
To apply, send me the following (contact links are below):
- Your laptop model
- Your macOS version (must meet the minimum)
- Your OpenCore version (v1.0.6 or later)
- Your fingerprint sensor
- Your VID:PID. Without this I can't use your help.
- Your timezone, so I don't ping you at 4AM (mine is UTC+3, KSA time)
- Whether your sensor is enabled in your USBMap or USBMap.kext. That decides whether it is powered at all. Check your USBMap, then System Information, USB, for the VID:PID.
Helping with code
This is what expands sensor support the fastest.
- The project is written in C, and the sensor code follows libfprint and fprintd conventions. If you know C, you're welcome. Anyone is welcome to try.
- Before a PR that adds a sensor backend or touches the build, check the
build_*.shscripts andci.yml. A new source file must be added everywhere the daemon's source list appears, or CI can pass green while the real build is broken. - For anything nontrivial (new backend, architecture change), open an issue first so we can align. Small fixes and typos can go straight to a PR.