Featured, Community and Testing tell you how an asset is curated and how mature it is. They do not tell you it was security reviewed. Treat the label as a hint about who stands behind the asset, then run your own checks on the code before it enters a build.
The three levels as Godot defines them
The Godot documentation for the Asset Library describes three support levels, and each asset belongs to exactly one.
| Level | What the documentation says | What it means for you |
|---|---|---|
| Featured | Hand-picked resources recognized for their value to the community | Someone chose it. That is a quality signal, not an audit |
| Community | Submitted and maintained by members of the Godot community | Maintained by volunteers. Response times will vary |
| Testing | Works in progress that may contain bugs and usability issues, not recommended for serious projects | Fine for experiments, not for a shipping game |
The documentation describes Testing assets as ones to download, test and report issues on. That is a reasonable stance for prototypes.
What an asset page shows you
An asset page lists its name, current version, category, Godot version, support status, original author, license, date of latest edit, a description and links for download, file list and issue tracker. Use all of it. A recent update date, a visible issue tracker and a clear license are cheap signals that someone is looking after the code.
Notice what is missing from that list: no field says that the code was reviewed for safety. The documentation also notes that features such as commenting and rating may come later, so there may be little community feedback on the page itself.
A decision guide
- Is the asset an editor plugin or a runtime script pack? A plugin.cfg file under addons/ marks an editor plugin. Editor plugins run in the editor, which raises the review bar. See the tool script post.
- Is it Featured, Community or Testing? Testing assets stay out of anything you ship.
- Does the version in the library match a tagged release in the source repository? If you cannot tell, ask or choose another asset.
- Does the license fit commercial use? Ask your own advisers for anything unclear. This post gives no legal advice.
- What does it load? Look for compiled libraries, network calls and scripts that run in the editor.
- Who will update it? Write down an owner.
Keep a record
Add each library asset to your inventory with name, version, support level at the time of download, license, source URL and reviewer. The inventory guide for engines, middleware and asset packs shows a simple layout.
Using the labels well
A sensible reading is that Featured and Community assets are candidates, and Testing assets are for experiments. Within candidates, rank by evidence you can check: update date, a working issue tracker, a clear license and code that is small enough to read. A tiny, readable addon from an active author is usually easier to trust than a huge one with no history.
Revisit the choice at each update. A label is a snapshot, and a Featured asset can still ship a version with a bug.
Where Safeguard fits
Safeguard offers SBOM and dependency scanning, policy gates and a free scan at https://gold.safeguard.sh/scan. Those tools work on declared dependencies. Library assets copied into a project folder still need the manual record above.
Quick check
Is a Featured asset safe?
Not automatically. Godot describes Featured as hand-picked for value to the community. That is curation, so still review the code you import.
Can I use a Testing asset in a shipped game?
Godot's documentation says Testing assets are not recommended for serious projects, so plan to replace or harden it before release.
Sources
Last reviewed: 19 October 2026.
