
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
@backstage/plugin-catalog-graph
Advanced tools
Disclaimer: If you are looking for documentation on the experimental new frontend system support, please go here.
Welcome to the catalog graph plugin! The catalog graph visualizes the relations between entities, like ownership, grouping or API relationships.
The plugin comes with these features:
EntityCatalogGraphCard:
A card that displays the directly related entities to the current entity.
This card is for use on the entity page.
The card can be customized, for example filtering for specific relations.
CatalogGraphPage:
A standalone page that can be added to your application providing a viewer for your entities and their relations.
The viewer can be used to navigate through the entities and filter for specific relations.
You can access it from the EntityCatalogGraphCard.
EntityRelationsGraph:
A react component that can be used to build own customized entity relation graphs.
To use the catalog graph plugin, you have to add some things to your Backstage app:
Add a dependency to your packages/app/package.json:
# From your Backstage root directory
yarn --cwd packages/app add @backstage/plugin-catalog-graph
Add the CatalogGraphPage to your packages/app/src/App.tsx:
<FlatRoutes>
…
<Route path="/catalog-graph" element={<CatalogGraphPage />} />…
</FlatRoutes>
You can configure the page to open with some initial filters:
<Route
path="/catalog-graph"
element={
<CatalogGraphPage
initialState={{
selectedKinds: ['component', 'domain', 'system', 'api', 'group'],
}}
/>
}
/>
Bind the external routes of the catalogGraphPlugin in your packages/app/src/App.tsx:
bindRoutes({ bind }) {
…
bind(catalogGraphPlugin.externalRoutes, {
catalogEntity: catalogPlugin.routes.catalogEntity,
});
…
}
Add EntityCatalogGraphCard to any entity page that you want in your packages/app/src/components/catalog/EntityPage.tsx:
<Grid item md={6} xs={12}>
<EntityCatalogGraphCard variant="gridItem" height={400} />
</Grid>
Copy the default implementation DefaultRenderNode.tsx and add more classes to the styles:
const useStyles = makeStyles(
theme => ({
node: {
…
'&.system': {
fill: '#F5DC70',
stroke: '#F2CE34',
},
'&.domain': {
fill: '#F5DC70',
stroke: '#F2CE34',
},
…
);
Now you can use the new classes in your component with className={classNames(classes.node, kind?.toLowerCase(), type?.toLowerCase())}
return (
<g onClick={onClick} className={classNames(onClick && classes.clickable)}>
<rect
className={classNames(
classes.node,
kind?.toLowerCase(),
type?.toLowerCase(),
)}
width={paddedWidth}
height={paddedHeight}
/>
<text
ref={idRef}
className={classNames(classes.text, focused && 'focused')}
y={paddedHeight / 2}
x={paddedWidth / 2}
textAnchor="middle"
alignmentBaseline="middle"
>
{displayTitle}
</text>
</g>
);
Once you have your custom implementation, you can follow these steps to modify the required components:
app.tsx update the CatalogGraphPage component to include your custom styles:<Route path=“/catalog-graph” element={<CatalogGraphPage renderNode={MyCustomRenderNode} />} />
Entity.tsx file, update the EntityCatalogGraphCard component to this:<EntityCatalogGraphCard variant=“gridItem” renderNode={MyCustomRenderNode} height={400} />
Implementers with added custom relations can add them to the catalog graph plugin by overriding the default API. This also allows some relations to not be selected by default.
In packages/app/src/apis.ts, import the api ref and create the API as:
import {
ALL_RELATIONS,
ALL_RELATION_PAIRS,
catalogGraphApiRef,
DefaultCatalogGraphApi,
} from '@backstage/plugin-catalog-graph';
// ...
createApiFactory({
api: catalogGraphApiRef,
deps: {},
factory: () =>
new DefaultCatalogGraphApi({
// The relations to support
knownRelations: [...ALL_RELATIONS, 'myRelationOf', 'myRelationFor'],
// The relation pairs to support
knownRelationPairs: [
...ALL_RELATION_PAIRS,
['myRelationOf', 'myRelationFor'],
],
// Select what relations to be shown by default, either by including them,
// or excluding some from all known relations:
defaultRelationTypes: {
// Don't show/select these by default
exclude: ['myRelationOf', 'myRelationFor'],
},
}),
}),
Run yarn in the root of this plugin to install all dependencies and then yarn start to run a development version of this plugin.

FAQs
Unknown package
The npm package @backstage/plugin-catalog-graph receives a total of 35,209 weekly downloads. As such, @backstage/plugin-catalog-graph popularity was classified as popular.
We found that @backstage/plugin-catalog-graph demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.