Observed
Relevant production-safety evidence is visible in the reviewed pull-request context.
Qedix documentation
Use these guides to connect selected repositories, understand Qedix results, manage access, and keep maintainers in control of merge and deployment decisions.
Follow the complete path from GitHub access to an evidence-informed review.
Understand the repository access requested by the currently configured Qedix GitHub App.
Review permissionsAn authorized GitHub administrator selects the organization and repositories that Qedix may review.
Open installation guideQedix analysis is triggered by supported pull-request activity in a connected repository.
Read the first-report guideUse the evidence, affected code, recommendation, and suggested verification as part of your normal review process.
View a sample reportQedix uses evidence states to separate visible controls from unproven assumptions and maintainer review.
Relevant production-safety evidence is visible in the reviewed pull-request context.
Qedix did not find enough visible evidence to establish the expected safety control.
The change needs application-specific context, verification, or maintainer judgment.
Use Qedix as one part of a complete engineering review process.
Qedix does not automatically approve, merge, deploy, or make the final release decision.
A clean result does not prove that software is secure, correct, compliant, deployable, or free from defects.
A suggested test is a recommendation for verification. It does not mean that Qedix executed the application or test suite.
Infrastructure, configuration, external services, and runtime behaviour may require separate testing and review.
Repository administrators remain responsible for Qedix installation scope.
Use GitHub App installation settings to add or remove selected repositories, subject to your GitHub authority.
Review permission guidance →An authorized GitHub administrator can remove future repository access by uninstalling the Qedix GitHub App.
Open uninstall guidance →