Community / Contributing

Help make the evidence useful.

Start with a behavior you can reproduce.

Source is available on GitHub. GitHub issues are open for bug reports, feature requests, and framework-support requests.

A useful bug report

• Your arnx version, OS, Docker version, language, and test runner.
• The command, expected behavior, and actual behavior.
• A small reproduction you have permission to share.
• Sanitized setup or review output and whether the failure repeats.
• For a questionable finding: why the generated test’s expectation differs from intended behavior.

Remove credentials, customer data, private repository names, and confidential code. Do not upload a complete .arnx/ directory without reviewing it. Security reports belong in a private email.

Request framework support

Name the language, runner, package manager, and required services. A small public example and the command that runs its tests make the request actionable. Explain where setup currently stops.

Contribute code or documentation

Read the canonical contributing guidelines. CONTRIBUTING.md explains how to get started. Use the issue forms for a bug, a wrong finding, or a model or prompt experiment. A wrong finding is the most useful report: tell us what the test expected and what the code is meant to do. Start larger changes with an issue describing the problem and proposed behavior. Keep changes focused, include a reproduction for bug fixes, run the repository’s checks, and preserve third-party attribution. arnx Open Source is licensed under Apache License 2.0.

Prefer a guided first run?

A guided pilot is optional onboarding and product research. Request a guided pilot by email. Please describe your language and runner.