OpenDPP Catalogue

Categories

Filters

Categories

Status

License

Technologies

Ontology

TracePath DPP Open Schemas

Active
Open-source machine-readable JSON schemas and GS1 Digital Link validation utilities for fashion, apparel, and footwear Digital Product Passports under the EU ESPR framework.
Python GS1 Digital Link JSON Schema
Ontology

TracePath DPP Open Schemas

TracePath DPP Open Schemas provides reusable, machine-readable JSON starter schemas and GS1 Digital Link validation utilities designed to support interoperable Digital Product Passport (DPP) experimentation for fashion, garments, textiles, and footwear. The schemas provide structured fields for product identity, material composition, country of origin, sustainability metrics, certifications, and SHA-256 snapshot hashes. The repository also includes a lightweight Python utility for checking a limited subset of GS1 Digital Link URI syntax and verifying GTIN check digits. The project is designed to support structured DPP data exchange between brands, suppliers, and other ecosystem participants without vendor lock-in, while supporting experimentation under the EU ESPR framework.

TracePath

v1.0.0

Python GS1 Digital Link JSON Schema
https://github.com/TracePath-eu/tracepath-dpp-open-schemas
https://github.com/TracePath-eu/tracepath-dpp-open-schemas/blob/main/README.md
Python 3.10+ (Standard Library: re, typing)
Ontology

Eclipse BaSyx DPP API

Open-source, standards-aligned DPP API that maps Digital Product Passports to Asset Administration Shells, with lifecycle, lookup, history and element-level operations.
Go JSON OpenAPI REST

Eclipse BaSyx DPP API

The Eclipse BaSyx Digital Product Passport API is an open-source Go service for creating and operating Digital Product Passports on Asset Administration Shell (AAS) infrastructure. Aligned with the IDTA-01001 v3.2 DPP metamodel annex and IDTA-01002 v3.2 DPP API mapping annex, it translates between API-facing DPP documents and modular AASs and Submodels. It can therefore expose existing BaSyx product twins through a DPP API or provide the backend for a new AAS-based DPP deployment.

Capabilities include creating, reading, updating and deleting DPPs; lookup by DPP ID or product ID; bulk product-ID resolution with pagination; retrieval of the passport version valid at a specified time; and element-level read and update operations. The service supports compressed JSON and expanded/full reads, PostgreSQL persistence, audit history, optional OIDC/ABAC route protection, optional tamper-evident WORM evidence and OpenTelemetry observability. Its OpenAPI contract, Swagger UI, Docker Compose example, sample battery passport, Postman collection and BaSyx Web UI integration support evaluation and deployment.

Typical use cases include battery passports and future ESPR product groups; publishing product identity, technical data, carbon footprint, material composition, circularity and handover documentation; integrating DPPs with existing AAS and digital-twin landscapes; and retaining traceable lifecycle changes for audits or after-sales access. The implementation supplies standards-aligned technical building blocks; regulatory compliance and product-specific data obligations remain the responsibility of each deployment.

Fraunhofer IESE

v1.0.9

Go JSON OpenAPI REST
https://github.com/eclipse-basyx/basyx-go-components
https://dpp.basyx.org/
Docker, PostgreSQL, OIDC, OTel
Full Digital Product Passport
ID

OpenEPCIS Digital Link Toolkit

Active
Apache 2.0 Java library, REST API and CLI for translating and validating GS1 identifiers between EPC URN and GS1 Digital Link URI, with canonical form output and QR code generation.
Quarkus GraalVM native GS1 Digital Link GS1 EPC Tag Data Standard Java
ID

OpenEPCIS Digital Link Toolkit

Every Digital Product Passport reached by scanning a GS1 QR code depends on one thing working correctly: the identifier in the code has to be well-formed, GS1-conformant, and reducible to a canonical form that every party agrees on. This library does that job.

It translates GS1 identifiers in both directions between EPC URN syntax and GS1 Digital Link Web URI syntax, at both instance and class level. Alongside the translation it returns the canonical Digital Link form on id.gs1.org, so identifiers captured against company-specific domains still compare and deduplicate correctly across systems.

A separate validator module checks identifiers against GS1 syntax rules, including check digit verification and Application Identifier constraints. Malformed identifiers fail at the boundary rather than propagating into a passport, a resolver entry or an event record. A QR code generator with configurable dimensions, colour and module shape is included for producing GS1 Digital Link carriers directly.

The library is usable three ways: as a plain Java dependency from Maven Central under io.openepcis, as a Quarkus extension with build-time optimisation and GraalVM native image support, and as a hosted REST API and web tool at tools.openepcis.io for anyone who wants to check an identifier without writing code.

Resolution tells you where a product’s data sits. A signature tells you who signed it. Neither tells you whether that party may speak for the identifier in the first place, and none of it works at all if the identifier itself is malformed. This library covers the syntactic floor that everything above it assumes.

It is deliberately narrow in scope and composes with resolvers, passport platforms and event repositories rather than duplicating them. Maintained by benelog GmbH & Co. KG, whose team co-chairs the GS1 EPCIS/CBV Standards Maintenance Group, and which additionally offers a commercially licensed GS1-conformant resolver service built on this open-source foundation.

benelog GmbH & Co. KG

0.9.4

Quarkus GraalVM native GS1 Digital Link GS1 EPC Tag Data Standard Java
https://github.com/openepcis/openepcis-epc-digitallink-translator
https://openepcis.io/docs/format-converter
Maven, ZXing for QR generation. Java, Quarkus
ID
Verifiable Credentials Schema

TracePass DPP-VC Profile

Active
EU Digital Product Passport field specifications as UNTP extension profile — JSON-LD contexts and W3C VC schemas for 12 product categories, every term traced to the EU law behind it.
JSON-LD JSON Schema (Draft 2020-12)
Verifiable Credentials Schema

TracePass DPP-VC Profile

A UNTP (UN Transparency Protocol) extension profile expressing EU Digital Product Passport requirements as JSON-LD contexts and W3C Verifiable Credential schemas. Twelve product categories — battery, textile, electronics, construction, iron & steel, chemicals, packaging, furniture, tyres, jewellery, toys, FMCG — plug into UNTP’s credentialSubject.characteristics extension point, contributing regulatory depth while UNTP keeps the credential, proof and interoperability.

868 properties, 90% citing the EU instrument or standard that defines the concept with a link to its EUR-Lex record; 222 carry a verified QUDT unit IRI. Where an established vocabulary already owns a concept it is reused rather than re-coined — GS1 for GTIN and batch identifiers, UN/CEFACT for economic operators and facilities, QUDT for units, CAS for substances. Terms with no existing owner are coined under a namespace that resolves: every tracepass: IRI returns a SKOS concept with a definition and a named owner. Each category ships a hand-authored worked example that validates against its schema. Extends UNTP DPP v0.7.0 by URI reference only — no UNTP artefact is vendored, keeping the Apache-2.0 licence clean against UNTP’s GPL-3.0 spec repository. Aligned with the EU DPP framework; not an official EU artefact and not legal advice.

TracePass LTD

0.1.0

JSON-LD JSON Schema (Draft 2020-12)
https://github.com/malinoto/tracepass-dpp-vc
https://github.com/malinoto/tracepass-dpp-vc#readme
—
Verifiable Credentials Schema

Transpareo Time Machine

Active
Embeddable DPP renderer: one custom element renders the passport, verifies its proofs in the visitor’s own browser, including selective-disclosure views, and scrubs a timeline through every version.
HTML SCSS JavaScript Shell TypeScript CSS

Transpareo Time Machine

The Transpareo Time Machine renders a Digital Product Passport as an interactive public page, and adds two things most DPP front-ends leave out: an auditable version history, and a verification verdict computed in the visitor’s own browser rather than read from a server’s “verified” flag.

Point the element at a manifest listing every version of a passport. It renders the current version up front, plus a timeline the visitor can scrub back through to replay every earlier state the passport has had, with EPCIS 2.0 ObjectEvents shown against the versions they produced. Each version’s snapshot carries a W3C Data Integrity proof set, and the renderer chooses its verification path from the proof’s cryptosuite. Whole-document snapshots (eddsa-jcs-2022, Ed25519) are canonicalized with RFC 8785 JCS; selective-disclosure snapshots (ecdsa-sd-2023, P-256) commit to each field on its own, so a view that reveals only the fields a given reader is entitled to still verifies against the issuer’s public key, with the withheld fields simply absent and nothing about them leaking. Either way the signatures are checked in the visitor’s browser via WebCrypto, with a bundled pure-JS fallback on engines lacking native Ed25519. The renderer also walks the priorVersionHash chain across both cryptosuites, hashing each link in its own format, so a removed or rewritten version becomes visible instead of silent.

Issuer and platform are treated as two independent authorities, and a compromised platform alone cannot make a passport verify. On a whole-document snapshot the proof set carries several issuer entries and several platform entries, and the default rule requires one verified entry from each side; a selective-disclosure snapshot carries the issuer’s proof and the platform’s counter-signature, each checked against the key its own verificationMethod resolves to. A platform key can be pinned for high-trust surfaces, and pinned keys are checked against a revocation list at boot.

It ships zero runtime dependencies. The reactive runtime, the JCS and RDFC canonicalizers, the multibase and CBOR decoders, and the Ed25519 and P-256 verifiers are all vendored: no React, Svelte, Lit, or Vue, and the VC and Transpareo JSON-LD contexts resolve offline. Delivery is a script tag from a CDN, an npm package for bundlers, or a self-hosted bundle. Theming is CSS custom properties, and 40 UI locales ship in the bundle, lazily loaded. A standalone element is included for checking a snapshot outside a passport page.

The renderer is storage-agnostic: it reads every artefact’s address from the manifest, so publishers host wherever they like.

Transpareo AG

2.5.1

HTML SCSS JavaScript Shell TypeScript CSS
https://github.com/transpareo/transpareo-time-machine
https://github.com/transpareo/transpareo-time-machine#readme
None at runtime (zero runtime dependencies, no UI framework). Build and dev only: Vite, TypeScript, Vitest, Playwright, Sass
Full Digital Product Passport

Open-dpp platform

Active
Open-Source platform to manage digital product passports
TypeScript Vue

Open-dpp platform

Our open-source Digital Product Passport (DPP) solution provides maximum transparency, flexibility, and data sovereignty. With no vendor lock-in, full visibility into the application and product roadmap, and extensive customization options, organizations remain in complete control of their digital product data.

Built on open standards such as the Asset Administration Shell (AAS), the platform integrates seamlessly into existing customer systems through a documented REST API and supports full data import and export. Flexible data models, role-based access control, and modular pricing allow companies to tailor the solution precisely to their needs.

Designed for European compliance requirements, the solution is GDPR-compliant, based on European open-source technologies, and hosted by a German cloud provider. For organizations requiring maximum control, a fully on-premise deployment option is also available.

open-dpp GmbH

v2.4.0

TypeScript Vue
https://github.com/open-dpp/open-dpp
NestJs, Docker
Full Digital Product Passport

Transpareo Time Machine

Active
Open-source Digital Product Passport renderer.
JavaScript CSS

Transpareo Time Machine

The Transpareo Time Machine is a single-page app (SPA) you embed as one custom element. Point it at a Digital Product Passport and it renders an interactive card: the product’s current details up front, and a timeline the visitor can scrub back through to replay every earlier version the passport has had. A verification chip on the card shows whether the data is authentic, checked cryptographically in the visitor’s own browser instead of taken on trust from a server.

Transpareo AG

v2.4.0

JavaScript CSS
https://github.com/transpareo/transpareo-time-machine
https://transpareo.com/en/transpareo-time-machine
None
Full Digital Product Passport

TracePass DPP Schemas

Active
Field specifications for EU Digital Product Passports across 12 product categories — 913 fields, each traced to the EU law that mandates it. Pure JSON, no build, any language.
JSON

TracePass DPP Schemas

An open dataset of the field-level requirements for EU Digital Product Passports, published as 12 plain-JSON category templates (battery, textile, electronics, construction, iron & steel, chemicals, packaging, furniture, tyres, jewellery, toys, FMCG). Every one of the 913 fields carries its data type, validation rules, 24 EU-language labels, and a structured citation to the instrument and provision that governs it (a 34-entry CELEX registry plus a canonical unit registry). 343 fields are required by an instrument currently in force; 187 are marked as anticipated under a named future instrument, so consumers can distinguish today’s legal obligations from expected ones.

The data is deliberately format-neutral: no runtime, no framework, no dependency on any hosted service or dataspace — a consumer can read the JSON directly or validate it against the bundled JSON Schema (Draft 2020-12). It is designed to be a citable reference for anyone implementing a DPP, and it interoperates with the semantic/VC layers in the catalogue rather than replacing them. Aligned with the EU DPP framework (ESPR 2024/1781 and the category instruments); not an official EU artefact and not legal advice.

TracePass LTD

0.1.1

JSON
https://github.com/malinoto/tracepass-dpp-schemas
https://github.com/malinoto/tracepass-dpp-schemas#readme
None. Pure JSON; optional validation via any JSON Schema (Draft 2020-12) validator. Also published on npm as `@tracepass/dpp-schemas` (with SLSA provenance) for JS/TS consumers.
Full Digital Product Passport