An open-source artifact metadata API for auditing and governing software supply chains.
Grafeas is an open-source artifact metadata API that provides a uniform way to audit and govern software supply chains. It defines an API specification for managing metadata about software resources like container images, VM images, and JAR files, offering organizations a central source of truth for tracking and enforcing policies across development teams and pipelines.
Platform engineers, DevOps teams, and security professionals who need to aggregate, audit, and enforce policies on metadata across diverse software components in their supply chain.
Grafeas offers a standardized, vendor-agnostic API that separates high-level metadata descriptions (notes) from their instantiations (occurrences), enabling fine-grained access control and allowing third-party providers to manage metadata on behalf of many customers.
Artifact Metadata API
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Defines a standardized API for diverse artifacts like container images and JAR files, enabling consistent auditing and policy enforcement across tools and teams.
Separates notes (metadata definitions) from occurrences (instances), allowing precise permissions for different metadata types, as highlighted in the concepts documentation.
Supports multiple backends including PostgreSQL and BoltDB, with community contributions for databases like Oracle and Elasticsearch, offering flexibility in deployment.
Provides libraries in Java, Go, Ruby, and Python, facilitating easy integration with various build, auditing, and compliance tools in existing pipelines.
Lacks a graphical interface, so teams must build custom dashboards for visualizing metadata, increasing development overhead for non-technical users.
Requires configuring storage backends and running the server locally, which can be non-trivial for new users, as noted in the running instructions.
Storage backends are planned to be extracted into separate projects (issue #341), potentially leading to breaking changes and additional maintenance effort.