# Verified publishers

> What the verified mark on a publisher means in SKaaS, how a publisher earns it, where an organization sees its state, and what it does not claim about the skills they publish.

Source: https://skaas.io/docs/verified-publishers
Last updated: 2026-11-14

The verified mark answers one question: does this publisher control the name it uses?

## How does a publisher become verified?

The organization creates a publisher profile on the **Publisher** page of its settings, or with the publisher route of the API. See [the public catalog](/docs/public-catalog). A person who runs the library, called the operator, then checks the proof and records it. The proof is control of a domain, shown with a DNS record, or ownership of a GitHub organization. The operator can also record a check that was made by hand. The record names the method and the domain or organization that was proved, and the library shows it.

The checking is done by a person. No automated DNS or GitHub check exists in the code, so a profile stays `pending` until the operator records the result. A deployment that has no operator credentials has no one to do this, and its publishers stay pending.

## What does the organization see?

The Publisher page shows the name in the library, the publisher address, the home page, the state (`pending`, `verified` or `suspended`), how it was verified and when, and the reports that people filed about the organization's skills, without the identity of the reporters. The owner can edit the display name and the home page there. A pending profile says what verification needs and that the operator does the review, so nothing on the page changes until they finish.

## What does the mark not mean?

It does not say that the skills are safe, reviewed or endorsed. It is a statement about identity, not about content. The audit badge on each release is a separate signal, and it has its own limits. See [the audit and its limits](/docs/auditor).

## Are releases signed?

Yes, when the organization has a signing key. Each release that it publishes then carries a signature, and the CLI checks the signature before it installs. Signing is a separate choice from verification, so a verified publisher's release can be unsigned, and a signed release can come from a publisher that was never verified. See [Signed releases](/docs/signed-releases).

## Where do I see the mark?

On catalog cards as plain text, and in the viewer as a badge that links here.
