Search for and delete attestations that you no longer need.
Attestations are only meaningful when they are linked to artifacts that people consume. To keep your attestations relevant and manageable, you should delete attestations that are no longer needed, such as:
When consumers have a verification process in place, deleting an attestation can prevent the associated artifact from being used. Consider setting up automations to ensure that attestations are deleted when the associated artifact is removed from an external service (for example, an image is deleted from a container registry).
Navigate to the repository where the attestation was produced.
Under your repository name, click Actions.

In the left sidebar, under "Management," click Attestations.
The attestations are sorted by creation date, newest first. Use the "Search or filter" bar to search for an attestation or filter the results.
Enter free text to search by subject name. This returns all attestations with subject names that partially match your search string. Multiple attestations can have the same subject name.
Use the created filter to filter by creation date. To enter a custom date range, click today's date then edit the default query.
created:<2025-04-03.> <.Use the predicate filter to filter by the kind of attestation. A predicate is the type of claim that an attestation makes about an artifact, such as "this artifact was built during a particular workflow run and originates from this repository."
attest action.attest action using the sbom-path input.Before deleting an attestation, we recommend downloading a copy of it. Once the attestation is deleted, consumers with a verification process in place will no longer be able to use the associated artifact, and you will no longer be able to find the attestation on GitHub.
To manage attestations in bulk with the REST API, see REST API endpoints for artifact attestations.