Trace software to its source
Every repository, and the company it actually belongs to.
Repositories drift across organizations, personal accounts and acquired teams. The inventory records where each one lives, who administers it, which product it serves and which entity is meant to own the result.
Repositories
- GitHub, GitLab & Bitbucket
- Repository-to-product mapping
- Administrators & custody
- Tags & releases
How it helps
What you get with Repositories
Across providers
GitHub first, with GitLab and Bitbucket following the same model, so a mixed estate is one inventory rather than three.
Admins are custody, not ownership
Repository administrators are recorded as operational custody. It is evidence about control, and deliberately not a conclusion about title.
Releases as anchors
Tags and releases give provenance something to attach to: what shipped, when, and out of which repository.
Software Provenance
The rest of Software Provenance
Connect repositories, contributors, agreements, components, releases and SBOM data to legal ownership.
Contributors & Agreements
Connect contributor identities and contribution periods to the agreements that cover their work.
Learn moreSoftware Products & Components
Model proprietary products, shared core components and brand-specific derivatives separately.
Learn moreSBOM & Third-Party Components
Import open-source and third-party component data from established standards.
Learn moreAI Models & Datasets
Track models, training and fine-tuning datasets, evaluation sets and related rights.
Learn moreBuild the ownership record before somebody asks for it.
Register what exists, connect the relationships, attach the evidence. The answer you need under deadline is the one you maintained beforehand.
Evidence-backed relationships Multi-entity by design Built for transfer and diligence