Skip to main content

Community resources

The Content Authenticity Initiative has an active and growing community of developers collaborating on the ecosystem of open-source tools and SDKs for working with digital content provenance creation and validation.

GitHub

All the open-source CAI code is hosted in GitHub in the CAI GitHub organization and we welcome input in the form of issues and pull requestsin the repositories:

If you think you've found a bug or want to request a feature, please open an issue in the appropriate repository.

We also welcome thoughtful pull requests (PRs) from the community, following the contribution guidelines provided out in each repository. The guidelines are generally the same for each of the three project repositories; for example. see the c2pa-rs contribution guidelines.

Participants are required to follow the Adobe Code of Conduct to maintain an open and welcoming environment for all.

These related projects may be of interest, but the CAI team doesn't maintain or support them:

  • Drupal module: Enables Drupal sites to process and display Content Credentials for supported image types.
  • DASH video player: DASH video player that displays Content Credentials in browsers for supported media types. This repo/branch is a work-in-progress forked from dash.js, the canonical reference JavaScript implementation for the playback of MPEG DASH.
  • TrustMark: Open-source Python implementation of watermarking for encoding, decoding and removing image watermarks.
  • C2PA Security Testing Tool: A CLI tool derived from c2patool that performs security testing on a Content Credentials application. This tool is intended for use by software security professionals.

Discussions on Discord

The CAI maintains a Discord server for open technical discussions within the developer community, with several text channels focused on different projects and topics.

Other resources

Developer questionnaire

Please fill out the Content Authenticity Initiative (CAI) Open-Source Implementation Questionnaire to let us know what you're building and how you're using the open-source tools and SDKs.