Product stage
Public beta
Qedix is currently available without a paid subscription or beta approval request.
Qedix Trust Center
Trust should be based on facts you can evaluate.
Use this center to understand what Qedix does, what access it requests, who controls decisions, how to interpret its evidence, and where the product’s limits begin.
Current product facts
A concise view of the public beta as it exists today.
Primary workflow
GitHub pull requests
Qedix reviews supported JavaScript and TypeScript changes in pull-request context.
Decision authority
Your maintainers
Results are advisory. Qedix does not automatically approve, merge, release, or deploy customer code.
Repository access
Administrator selected
GitHub administrators choose the repositories available to the Qedix GitHub App.
Result model
Evidence-oriented
Reports connect recommendations to affected code and visible or missing evidence.
Repository source handling
Temporary processing
Qedix does not retain a persistent full copy of a repository. Selected metadata, analysis results, affected file references, and limited redacted evidence excerpts may be retained.
Detection guarantee
No absolute guarantee
A clean result does not prove that code is defect-free, secure, or ready for every production environment.
How to interpret Qedix evidence
Reports support engineering judgment; they do not replace it.
Affected code and context
A useful result should help the reviewer understand which changed code is relevant and why it deserves attention.
Observed evidence
Reports may identify evidence visible in the available code or explain when expected evidence is not visible in the analyzed context.
Reasoned recommendation
Recommendations should be treated as review input that a maintainer evaluates against the application’s real requirements and operating environment.
Suggested verification
Suggested tests describe checks a team may perform. They are not represented as tests that Qedix executed unless the product explicitly provides executed-test evidence.
A practical evaluation path
A controlled way for engineering teams to evaluate Qedix during the public beta.
- 01
Review the requested access
Read the permissions guide and confirm that each GitHub permission matches your organization’s expectations.
Permissions guide - 02
Install on selected repositories
Begin with repositories that are appropriate for evaluation and expand access only when your administrators are comfortable.
Installation guide - 03
Inspect the first report
Evaluate whether the report identifies affected code, explains the concern, and clearly separates observations from recommended verification.
First-report guide - 04
Keep existing controls
Continue using tests, type checking, linting, security tooling, human review, staging, and deployment approval.
Documentation
Shared responsibility
Qedix provides review evidence; customers retain responsibility for their software and workflows.
Qedix provides
- Advisory production-readiness evidence for supported pull-request changes.
- Customer-facing explanations of requested GitHub access.
- Documentation for installation, report interpretation, and uninstallation.
- A private process for reporting suspected security concerns.
Your team remains responsible for
- Deciding which repositories and users are appropriate for the service.
- Reviewing findings and validating recommendations against real application requirements.
- Testing, approving, releasing, deploying, and monitoring customer software.
- Protecting GitHub accounts, credentials, tokens, and organization administration.
Public trust resources
Use the source that matches the question your team is evaluating.
Security overview
GitHub access, customer controls, security boundaries, and vulnerability reporting.
Permissions
The current GitHub App permissions and the visible purpose of each permission.
Privacy
Information about data categories, purposes, choices, and privacy-related requests.
Terms
The conditions and responsibilities associated with using the Qedix public beta.
Responsible disclosure
How to privately report a suspected security vulnerability involving Qedix.
Uninstallation
How administrators can remove repository access or uninstall the GitHub App.
What remains private
Transparency does not require publishing information that would weaken the product or customer safety.
Last reviewed: July 14, 2026. Product-stage and pricing statements describe the current public beta and may change with future releases.