Trace software to its source
Every commit has an author. Not every author has an agreement.
The gap that derails software diligence is almost always the same one: a contractor who wrote a meaningful part of the product during a period no assignment covers. Intangible HQ looks for that gap continuously, while the person is still reachable.
Contributors & Agreements
- Contributor identity matching
- Agreement coverage windows
- Contribution summaries
- Coverage exceptions
How it helps
What you get with Contributors & Agreements
Identity matching
Commit identities, accounts and people are reconciled, so one contributor with three email addresses is one contributor.
Coverage windows
An agreement covers a period. Contributions outside that period are exceptions to resolve, not footnotes to discover later.
Evidence, not accusation
A coverage gap is a work item with the contributions, dates and documents attached — everything needed to fix it quickly.
Software Provenance
The rest of Software Provenance
Connect repositories, contributors, agreements, components, releases and SBOM data to legal ownership.
Repositories
Inventory repositories, organizations, releases and technical custody.
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