# Cosign

Cosign is a signing and verification tool for OCI (open container image) images and other artifacts that uses Sigstore to let developers prove authenticity and help operators confirm software has not been tampered with. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5296/cosign

## Description

Cosign is a signing and verification tool for OCI (open container image) images and other artifacts that uses Sigstore to let developers prove authenticity and help operators confirm software has not been tampered with.

## Platform availability

Available on 0 of 10 platforms.

## Health score

76/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 3 days ago)
- Popular: 76 (6,449 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 80 (no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 7.7/10)

## Links

- GitHub: https://github.com/sigstore/cosign
- Docker Hub: https://hub.docker.com/r/bitnami/cosign

## Common questions

### Do I need to log in to a private registry before signing an image?

Yes, if the registry requires a login, run cosign login with your username and password. Without those credentials, Cosign may not be able to store the signed proof attached to your image.

### How do I use my own Sigstore signing services instead of the public service?

Create a signing config JSON file with cosign signing-config create that lists the service URLs to use. Without that file, Cosign does not know which custom services to contact for signing.

### How should I protect a local Cosign signing key?

Keep the local key file safe and readable only by you. If you lose it, you cannot sign new images with that key, and if someone else gets it, they can create signatures that appear to be yours.

### Where can I apply Cosign in a self-hosted container build pipeline?

You can use keyed or keyless Cosign flows and verify images against the Rekor transparency log. It can be integrated with Gitea or Forgejo Actions and Woodpecker, with policy enforcement at the docker-compose hook level.

---
Source: Our Local Host (https://ourlocalhost.com/app/5296/cosign), the self-hosted and open-source app directory.
