Trust labels and portability levels explained
What Official, Verified Publisher, Security Checked, Featured and Community each mean, and what Portable, Compatible and PGB Native tell you.
Anyone can publish on PGB Marketplace, so each package shows a few separate signals. They answer different questions, and one never implies another. A full explanation is on the Marketplace's How trust works page.
Trust labels
- Official: published by PGB itself.
- Verified Publisher: PGB has confirmed who the publisher is. This says nothing about the package's quality.
- Security Checked: this version passed PGB's automated package checks, covering structure, permissions and exposed secrets. It is not a manual review and not a guarantee.
- Featured: chosen by the PGB team for the front page. It is an editorial pick, not a safety rating.
- Community: published by an independent author who is not verified. Read the permissions before you install.
A package can carry several labels, for example Official and Security Checked.
Portability
Portability shows how tied a package is to PGB:
- Portable: works on its own. No PGB services are needed, so you can take it anywhere. Many starter functions, such as CSV to JSON, are portable.
- Compatible: follows open conventions and works best on PGB, with small adjustments needed elsewhere.
- PGB Native: built for PGB and uses PGB features directly.
Use the Portability filter on Browse to narrow a search.
Permissions and risk
Each package lists what it may access in plain words, with a risk level of Low risk, Medium risk or High risk. Low means things like writing drafts; medium means reading your mail or data; high means sending, sharing, changing data or contacting outside services. See Review permissions and install.
Deprecated and yanked
A Deprecated banner means the publisher recommends something else. A Yanked version was withdrawn by its publisher and cannot be newly installed, though existing installs keep working.
Good to know
- Treat labels as one input, not a verdict. A Verified Publisher can still publish something you do not need.
- A package that asks for sensitive access or contains code stays unlisted until PGB has reviewed it.
- Something wrong? Use Report this package. See Review, yank, deprecate and report.
More guides in PGB Marketplace
Browse and search PGB Marketplace
Find agents, tools, integrations, functions, templates and workflows by type, category, portability and keyword.
Review permissions and install a package
Choose where a package goes, read exactly what it can access, fill in its settings and confirm the install.
See and remove what you have installed
The My installs page lists every package you installed and anything installed on projects you manage, with an Uninstall button.
Become a publisher and add your team
Create a publisher, understand names and roles, and invite teammates to publish with you.
Write the package manifest (pgb.package.json)
The one file that describes your package: name, type, version, permissions, settings and secrets, with the rules each field must follow.
Template variables: the settings form for your template
Define the fields people fill in, how they are grouped and shown, and which files stay locked, in the template block of your manifest.