Files
backstage/plugins
MT Lewis ed4ffaa3b3 fix(auth-backend): default catalog presence check to on, rename config
Address review feedback: flip the catalog user existence check to
enabled by default and rename the config option to
`dangerouslyDisableCatalogPresenceCheck` as an escape hatch. Also use
`error.name` instead of `instanceof` for cross-realm error safety.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: MT Lewis <mtlewis@users.noreply.github.com>
2026-05-07 16:52:13 +01:00
..
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-05 14:57:07 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-05 14:57:07 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-05 14:57:07 +00:00
2026-05-05 14:57:07 +00:00

Plugins

Backstage is a single-page application composed of a set of plugins. This folder holds numerous plugins that are managed by this repository. However, most plugins are in the community plugins repo - hop over there if you want to contribute!

For more information about the plugin ecosystem, see the documentation here:

https://backstage.io/docs/plugins/

You can also see the Plugin Marketplace for other open source plugins you can add to your Backstage instance.

Suggesting a plugin

If you start developing a plugin that you aim to release as open source, we suggest that you create a new Issue on the community plugins repo. This helps the community know what plugins are in development.

You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work.