Verified organisations and badges
What "Official", "By Denofy", "Verified Org" and "Community import" mean, and how a company verifies its GitHub organisation.
Updated 17 Oct 2026 1 min read
Anyone can publish on Denofy, and anyone can import openly licensed work. The badges tell you who stands behind a package.
| Badge | Meaning |
|---|---|
| Official | Published by a verified organisation from one of its own GitHub repositories. Only this badge says Official. |
| By Denofy | Maintained by the Denofy team (the example skills). |
| Verified Org | Belongs to a verified organisation, but does not come from one of its repositories. |
| Community import | Someone else's work, imported from a public repository with its license and attribution. |
How an organisation is verified#
- A member registers the organisation under Dashboard → Organisations with its GitHub login.
- They verify it with GitHub: Denofy checks that their account is an owner (admin) of that GitHub organisation. Optionally the website domain is verified with a DNS TXT record.
- Only after a successful verification does the organisation get a public page and appear next to its packages. Until then it is visible to its members only — so nobody can appear as a well-known company without proof.
Packages from the organisation's own repositories then show Official. Imports of the same work by other people stay Community import until the organisation claims them.
Details for organisations: Organisations.