Transparency Exchange API

Publishing an SBOM is not the same as being transparent.

An SBOM emailed to a customer answers one question, once, for one person. The OWASP Transparency Exchange API makes it an endpoint instead: a consumer starts from a single identifier, resolves it through DNS, and walks a standard object graph to the exact artifact they need, without asking you for anything. Vulnesis analyses millions of open-source packages across dozens of ecosystems, and serves TEA 1.0.0, and 0.4.0 for clients that pin it, over your own software and over the open-source projects it depends on, through the same API. It also ships a client, so you can browse your suppliers' endpoints the same way they browse yours.

Request a demo

There is no third party.

Five object types, and a path between any two

Every format your scans already produce

Conformance we measured, not conformance we claim

Ask a question, get a CycloneDX document

"Should I still be running this?"

Two answers, and the graph builds itself

A client as well as a server

The obligation is arriving whether the tooling is ready or not

Consume our server the way we consume yours

Get a free API key  ยท  Open it in the Resolve Platform