Community

PhoinixDR is developed in the open by @pcoronaf. Everything happens on GitHub.

Issues

Bug reports and feature requests. For a recovery that went wrong, include the phoinix explain output or the scan log from the desktop's Advanced mode (Copy scan log) and, when you can, an image of the volume.

Discussions

Questions, recovery stories, ideas and design conversations.

Contributing

How the workspace is organised, the coding rules (read-only, no panics on malformed media, conservative dependencies) and how to add a filesystem engine or a carving signature.

Security

The threat model and how to report a vulnerability privately.

Code of conduct

What we expect from each other.

Test on real hardware

A repeatable procedure for trying PhoinixDR on your own USB sticks and disks and reporting what you see.

Ways to help

Try it on a real device and report both successes and failures with the evidence PhoinixDR prints.
Contribute fixtures: small disk images with known content and deletion scenarios make the recovery engines verifiable.
Review the engineering: filesystem parsers, the health model and the decision records are meant to be challenged. See the Development Declaration.
Documentation and translations.

Roadmap

Milestones M0 to M11 of the technical specification are implemented. Next: calibration of the health model on larger corpora, HFS+/APFS, XFS/Btrfs, LVM and RAID reassembly. Follow the changelog.