Get involved
You don't have to be a reverse engineer
The scarce input is evidence: reproducible observations of what the original software does. Find your route below.
Scientists & instrument owners
Contribute representative files, software versions, manuals, calibration records, expected results, and reproducible observations of what the original software does. You don't need to write code.
Note: Never upload proprietary installers or sensitive laboratory data to a public repository.
Developers & reverse engineers
Investigate file formats, numerical operations, instrument protocols, native binaries, and application behavior; build independent implementations and tests.
AI-assisted contributors
Take a bounded issue, follow the repository instructions, reproduce the failing test on public fixtures, implement, produce evidence, and submit a reviewed pull request.
The rule that matters most
Never claim compatibility that has not been verified against documented reference behavior. A pull request distinguishes what it newly implements, which tests ran and their result, what reference evidence backs the behavior, and what remains unverified.
Tests, two tiers
Implementation repositories expose just test — deterministic tests that need no proprietary software and gate every pull request — and just test-reference, optional tests against a licensed original or a physical instrument. Reference tests are never a hidden prerequisite.
Start here
- Contribution guide
- Research repository— propose a target or a finding.