Review, yank, deprecate and report
Why a version may wait for review, how to withdraw or retire a package, and how anyone can report a problem.
When a package is reviewed
Publishing is open, but some versions stay unlisted until a PGB reviewer approves them. That happens when the package:
- asks to contact outside services (
network.outbound), - asks to change project data (
database.write), - asks to send or share from PGB Business, or
- contains executable code.
Until it is approved, only you and your team can see it. On Manage this package, Review status says which versions are pending. If a reviewer does not approve a version, it is Not listed; publish a new version that addresses their concerns. Packages from PGB itself are approved automatically.
Yank a version
Yank a version if it has a serious problem.
- Open Publish, choose Manage on your package.
- Under Versions, choose Yank on the version.
- Give a reason and choose Yank version.
Yanking stops new installs. Existing installs keep working. You cannot undo it, and the version number can never be used again.
Deprecate a package
Deprecation warns people without removing anything.
- On Manage this package, open Deprecate.
- Optionally type a message (up to 300 characters), such as "replaced by @acme/new-package".
- Choose Mark as deprecated.
The package page then shows a Deprecated banner. It stays installable. Use Update deprecation or Remove deprecation later.
Report a package
Anyone signed in can report a package.
- Open the package and choose Report this package.
- Under What's the problem? choose: Harmful or malicious behaviour, Spam or misleading listing, Copyright or trademark, Does not work, Inappropriate content or Something else.
- Add optional Details (up to 2,000 characters).
- Choose Send report.
The PGB team looks at every report. You do not need to do anything else.
Good to know
- Labels such as Security Checked describe automated checks only. See Trust labels and portability.
- Prefer a new version over a yank when you only need to fix something small.
- Keep your listing summary accurate; misleading listings can be reported.
More guides in PGB Marketplace
Browse and search PGB Marketplace
Find agents, tools, integrations, functions, templates and workflows by type, category, portability and keyword.
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.
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.