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…

  • Infrastructure
  • Security
  • Tools & Utilities
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 3 days ago
Popular
766,449 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
80no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 7.7/10

Based on 4 of 5 factors.

GitHub stars
6,449
Open issues
147
Last commit
2026-11-18
Latest release
v3.1.4
License
Apache-2.0
Activity
steady

Checked 3 days ago - source: GitHub (sigstore/cosign)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Log in to your image registry If the place where your container image is stored requires a login, run `cosign login <registry> -u <username> -p <password>` before signing or uploading signatures. Without these credentials, Cosign may not be able to store the signed proof attached to your image. source
  • Keep your local signing key safe If you sign with a local key file such as `cosign.key` (the private key Cosign uses), keep it safe and only readable by you. If you lose it, you can't sign new images with that key, and if someone else gets it, they can make signatures that appear to be yours. source
  • Create a signing config for custom services If you run your own signing services instead of the public Sigstore signing service, use `cosign signing-config create` to make a JSON file that lists the service URLs to use. Without that file, Cosign won't know which custom services to contact for signing. source
  • Signing Use the default keyless signing flow with Sigstore Fulcio and Rekor. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com, github.com, github.com, www.bigiron.cc

Community

Collected 48 days ago - public community threads