Repository valuation and licensing
How CodeMerchant evaluates private repositories
Understand the evidence, limitations, and data-handling rules before you scan or submit your work.
What is CodeMerchant?
CodeMerchant evaluates private GitHub repositories for engineering quality, privacy risks, provenance, and indicative licensing value. It helps developers and companies prepare existing work for potential licensing or sale to data vendors and AI labs.
What does a repository scan check?
Reports examine GitHub history, language mix, tests and committed coverage evidence, documentation, workflows, estimated complexity, and engineering depth. Privacy checks look for credential and personal-data patterns; provenance checks include public-history signals. Reports distinguish measured, estimated, agent-reviewed, and unavailable evidence.
Does CodeMerchant execute my code or tests?
No. Repository code, CI workflows, and tests are not executed during a scan. Quality signals come from static analysis and available metadata. A detected test file or coverage artifact is evidence, not proof that the current revision passes its tests.
Is the displayed valuation a purchase offer?
No. It is an indicative rubric-based estimate, not a guaranteed payment or purchase offer. Actual earnings depend on buyer demand, completed sales, and the agreed license. A scan does not guarantee a buyer or certify ownership, privacy, or commercial suitability.
How are private source and uploaded context handled?
Repository source is processed in bounded memory and discarded after scanning; reports retain derived evidence such as categories, counts, scopes, and paths. Supplemental files are retained privately for admin review and future analysis, including when extraction fails. The Privacy Policy describes providers and retention; the Data License governs authorized evaluation and commercial uses.
Who can submit a repository?
Submit only work you are authorized to provide under the Data License. Review ownership, contributor rights, third-party licenses, and sensitive information first. Connecting a GitHub account does not by itself establish the right to license a repository or its contents.
Can I include project context?
Yes. You can optionally attach project materials such as task-tracker exports, documentation, and other authorized context. More context can help explain the engineering work, but it does not guarantee a higher valuation or sale.
Review the terms before you start
The Data License governs submitted materials and commercial rights. The Privacy Policy explains retention, service providers, and your choices.
Questions? Contact CodeMerchant.
Get started with CodeMerchant