Skip to content
The platform

Trace software to its source

From contributor to code to current owner.

A repository proves that code exists; it does not prove who owns the rights in it. Intangible HQ connects development evidence to contributor agreements and assignment records so software chain of title becomes continuously inspectable instead of reconstructed under deadline.

How it helps

Why teams rely on Software Provenance

1

Repository metadata with legal context

Connect GitHub, GitLab or Bitbucket repositories to the software products, brands and entities they actually support.

2

Contributor coverage

Match developer identities to employment or contractor agreements, and flag contribution periods no agreement covers.

3

Import composition, do not rebuild scanners

Ingest SPDX or CycloneDX from the tools you already run. Intangible HQ is the ownership layer, not another vulnerability scanner.

Build 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