Software
License your engineering history to qualified buyers.
Valite licenses repositories, pull requests, issues, and CI history for research and product development, under terms you approve.
Licensing scope
What a dataset includes
Repositories
Full git history for each included repository.
Linked records
Issues, pull requests, and review comments, with author names replaced.
Documentation
A list of included and excluded paths, and the license audit.
How it works
We license the full history.
Each change is delivered with its issue, commits, review comments, and check results.
Scope the key per merchant. Two merchants can reuse an event ID after a migration.
We remove secrets and third-party code.
Repositories collect API keys, internal hostnames, and vendored open-source code under licenses that don’t permit relicensing. We find all three and remove them before review.
We flag code the company may not own.
Code written by employees belongs to the company. Commits from contractors without a signed IP assignment are flagged for you to confirm.
| Contributor ID | Commits | Code owned by company |
|---|---|---|
| 1014 | 4,812 | Yes · employee |
| 1027 | 3,960 | Yes · employee |
| 1031 | 1,204 | Yes · contractor |
| 1052 | 318 | To confirm |
Questions and answers
Does a buyer get our product?
No. The license is limited to internal research and development. Buyers can’t run, ship, or resell your code, and you can leave out any repository.
Are developer names included?
No. Author names and emails are replaced with consistent pseudonyms.
What about forks of open-source projects?
Only your own changes are licensed. Upstream code stays under its original license and is removed.
How is the code delivered?
As repository mirrors with full history, or through a clean room where appropriate.