PageSourceSearch

https://ratify.dev/assets/js/1337a255.ed6e8575.js

js ratify.dev collected 2026-09-24 19:29:33 UTC 9,663 bytes, 1 lines download raw bytes

1"use strict";(globalThis.webpackChunkratify=globalThis.webpackChunkratify||[]).push([[4666],{76122(e){e.exports=JSON.parse('{"version":{"pluginId":"default","version":"2.0.0-beta.1","label":"2.0.0-beta.1","banner":"unreleased","badge":true,"noIndex":false,"className":"docs-version-2.0.0-beta.1","isLast":false,"docsSidebars":{"tutorialSidebar":[{"type":"link","href":"/docs/2.0.0-beta.1/what-is-ratify","label":"What is Ratify","docId":"what-is-ratify","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/quick-start","label":"Getting Started","docId":"quick-start","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/ratify-configuration","label":"Configuration","docId":"ratify-configuration","unlisted":false},{"type":"category","label":"Concepts","collapsible":true,"collapsed":true,"items":[{"type":"link","href":"/docs/2.0.0-beta.1/concepts/executor","label":"Executor","docId":"concepts/executor","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/concepts/ratify-framework-overview","label":"Framework Overview","docId":"concepts/ratify-framework-overview","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/concepts/store","label":"Store","docId":"concepts/store","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/concepts/verifier","label":"Verifier","docId":"concepts/verifier","unlisted":false}],"href":"/docs/2.0.0-beta.1/category/concepts"},{"type":"category","label":"Plugins","collapsible":true,"collapsed":true,"items":[{"type":"category","label":"Store","collapsible":true,"collapsed":true,"items":[{"type":"link","href":"/docs/2.0.0-beta.1/plugins/store/oras","label":"Registry Store","docId":"plugins/store/oras","unlisted":false}]},{"type":"category","label":"Verifier","collapsible":true,"collapsed":true,"items":[{"type":"link","href":"/docs/2.0.0-beta.1/plugins/verifier/notation","label":"Notation","docId":"plugins/verifier/notation","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/plugins/verifier/cosign","label":"Cosign","docId":"plugins/verifier/cosign","unlisted":false}],"href":"/docs/2.0.0-beta.1/plugins/verifier/"}],"href":"/docs/2.0.0-beta.1/category/plugins"},{"type":"category","label":"Reference","collapsible":true,"collapsed":true,"items":[{"type":"link","href":"/docs/2.0.0-beta.1/reference/instrumentation","label":"Instrumentation","docId":"reference/instrumentation","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/reference/logger","label":"Logger","docId":"reference/logger","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/reference/multi-tenancy","label":"Multi-tenancy","docId":"reference/multi-tenancy","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/reference/security","label":"Security","docId":"reference/security","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/reference/usage","label":"Usage","docId":"reference/usage","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/reference/verification-result-version","label":"Verification Response","docId":"reference/verification-result-version","unlisted":false}],"href":"/docs/2.0.0-beta.1/category/reference"},{"type":"category","label":"Support and Troubleshooting","collapsible":true,"collapsed":true,"items":[{"type":"link","href":"/docs/2.0.0-beta.1/troubleshoot/errors","label":"Errors in Ratify","docId":"troubleshoot/errors","unlisted":false},{"type":"link","href":"/docs/2.0.0-beta.1/troubleshoot/installation-tips","label":"Installation FAQ","docId":"troubleshoot/installation-tips","unlisted":false}],"href":"/docs/2.0.0-beta.1/category/support-and-troubleshooting"}]},"docs":{"concepts/executor":{"id":"concepts/executor","title":"Executor","description":"The executor is the \'glue\' that links all Ratify plugin-based components such as the verifiers, referrer stores, and policy providers. The executor handles all components of the verification process once a subject verification request is received either via CLI or server.","sidebar":"tutorialSidebar"},"concepts/ratify-framework-overview":{"id":"concepts/ratify-framework-overview","title":"Framework Overview","description":"Ratify is a verification engine that c
1oordinates the verification of supply chain artifacts (signatures, SBOMs, attestations, and other metadata) associated with an image, and produces a single trust decision that an admission controller such as OPA Gatekeeper can act on.","sidebar":"tutorialSidebar"},"concepts/store":{"id":"concepts/store","title":"Store","description":"A referrer store (or store) discovers and retrieves artifacts and their referrers (signatures, SBOMs, and other metadata) for a subject image. Stores are one of the pluggable components that the Executor coordinates during verification.","sidebar":"tutorialSidebar"},"concepts/verifier":{"id":"concepts/verifier","title":"Verifier","description":"A verifier validates a specific artifact type (for example a signature) associated with a subject image and returns a verification report. Verifiers are one of the pluggable components that the Executor coordinates during verification.","sidebar":"tutorialSidebar"},"plugins/store/oras":{"id":"plugins/store/oras","title":"Registry Store","description":"registry-store is the built-in Ratify store for OCI-compliant registries. It uses the ORAS oras-go library to authenticate to a registry and to discover, list, and download a subject\'s referrer artifacts (signatures, SBOMs, and other metadata).","sidebar":"tutorialSidebar"},"plugins/verifier/cosign":{"id":"plugins/verifier/cosign","title":"Cosign","description":"cosign is a built-in Ratify verifier that validates Sigstore Cosign signatures. It supports both keyless (certificate identity + OIDC issuer) and key-based verification.","sidebar":"tutorialSidebar"},"plugins/verifier/index":{"id":"plugins/verifier/index","title":"Verifiers","description":"Ratify v2 ships with built-in verifiers, selected by type in the verifiers list of an Executor. There are no external/binary verifier plugins in v2.","sidebar":"tutorialSidebar"},"plugins/verifier/notation":{"id":"plugins/verifier/notation","title":"Notation","description":"notation is a built-in Ratify verifier that validates Notary Project signatures. It uses X.509 PKI with a trust store (certificates) and trusted identities to determine whether a signed artifact is authentic.","sidebar":"tutorialSidebar"},"quick-start":{"id":"quick-start","title":"Getting Started","description":"Try out Ratify v2.0.0-beta.1 in Kubernetes through Gatekeeper as the admission controller.","sidebar":"tutorialSidebar"},"ratify-configuration":{"id":"ratify-configuration","title":"Configuration","description":"This document provides comprehensive guidance on configuring Ratify executors using Kubernetes Custom Resources (CRDs). It covers all executor components including verifiers with their key providers, stores for artifact retrieval, and policy enforcers for verification criteria. Key providers are configured directly within the verifier configuration rather than as separate resources.","sidebar":"tutorialSidebar"},"reference/instrumentation":{"id":"reference/instrumentation","title":"Instrumentation","description":"This page outlines current instrumentation support in Ratify. It also contains guides for installing metrics providers and supported dashboards.","sidebar":"tutorialSidebar"},"reference/logger":{"id":"reference/logger","title":"Logger","description":"Overview","sidebar":"tutorialSidebar"},"reference/multi-tenancy":{"id":"reference/multi-tenancy","title":"Multi-tenancy","description":"Ratify v2 supports multi-tenancy through the namespaced NamespacedExecutor custom resource, allowing multiple teams to share a single cluster while each manages its own verification configuration.","sidebar":"tutorialSidebar"},"reference/security":{"id":"reference/security","title":"Security","description":"Refer to vulerability management and release documentation here.","sidebar":"tutorialSidebar"},"reference/usage":{"id":"reference/usage","title":"Usage","description":"This page documents useful flags and options supported by Ratify","sidebar":"tutorialSidebar"},"reference/verification-result-version":{"id":"reference/verification-result-version","title":"Verification Response","description":"Verification Response is the data returned for external data request calls. As we add new features, the Verification Response may change its format. To make it easy for users and other developers to work with different formats, we have implemented versioning support. This document lists all the versions of the Verification Response that have ever existed and will be updated whenever we make a new change to the format.","sidebar":"tutorialSidebar"},"troubleshoot/errors":{"id":"troubleshoot/errors","title":"Errors in Ratify","de
1scription":"Ratify can generate various errors, either from its core workflow or from external/internal plugins. To facilitate easier debugging, Ratify will throw an error with a code property in most cases. This code can be used to identify the error and provide a more meaningful error message.","sidebar":"tutorialSidebar"},"troubleshoot/installation-tips":{"id":"troubleshoot/installation-tips","title":"Installation FAQ","description":"Please use `kubectl describe` or `kubectl logs` to see the installation error.","sidebar":"tutorialSidebar"},"what-is-ratify":{"id":"what-is-ratify","title":"What is Ratify","description":"Ratify is a verification engine as a binary executable and on Kubernetes which enables verification of artifact security metadata and admits for deployment only those that comply with policies you create.","sidebar":"tutorialSidebar"}}}}')}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.