Thanks for using our plugin created for retrieving OWASP's Dependencytrack information in Backstage. This plugin is still in development.
Run this command from the app package directory:
yarn add @trimm/plugin-dependencytrackInstall the alpha entry point in apps that use Backstage's new frontend system:
import dependencytrackPlugin from '@trimm/plugin-dependencytrack/alpha';
const app = createApp({
features: [
dependencytrackPlugin,
// other plugins
],
});The alpha entry point auto-registers:
- the Dependencytrack API client
- the summary entity card on compatible catalog entities
- the
Dependencytrackentity tab at/dependencytrack
Use the root entry point if you still need the legacy app-wired extensions.
Add config in app-config.yaml.
Integration:
dependencytrack:
baseUrl: ${DEPENDENCYTRACK_BASE_URL}Proxy:
proxy:
endpoints:
'/dependencytrack':
target: ${DEPENDENCYTRACK_BASE_URL}
allowedMethods: ['GET']
headers:
X-Api-Key: ${DEPENDENCYTRACK_API_KEY}Don't forget to replace the variables with the values for your specific environment.
// packages\app\src\components\catalog\EntityPage.tsx
import { EntityDependencytrackSummaryCard, EntityDependencytrackFindingCard, isDependencytrackAvailable } from '@trimm/plugin-dependencytrack';
// In the overviewContent. You can add one or both.
// Metrics card
<EntitySwitch>
<EntitySwitch.Case if={isDependencytrackAvailable}>
<Grid item md={6}>
<EntityDependencytrackSummaryCard/>
</Grid>
</EntitySwitch.Case>
</EntitySwitch>
// Findings card
<EntitySwitch>
<EntitySwitch.Case if={isDependencytrackAvailable}>
<Grid item md={12}>
<EntityDependencytrackFindingCard/>
</Grid>
</EntitySwitch.Case>
</EntitySwitch>If you want to install only selected Dependencytrack entity extensions in a new frontend system app, import the named exports from the alpha entry point instead of the default plugin:
import {
EntityDependencytrackSummaryCard,
EntityDependencytrackFindingCard,
EntityDependencytrackContent,
} from '@trimm/plugin-dependencytrack/alpha';Reference the DependencyTrack project from your catalog-info.yaml in one of two ways.
By project name (recommended when the project carries one version per build). The plugin resolves the project's latest version through DependencyTrack's isLatest flag at read time, so the link always follows the current build and never needs re-pinning:
# Example catalog-info.yaml entity definition file
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
# ...
annotations:
dependencytrack/project-name: my-service # the DependencyTrack project nameBy project id (a fixed version UUID). Pins one specific project version:
metadata:
# ...
annotations:
dependencytrack/project-id: e63d5397-5e9e-494a-4755-368c2b1dc446If both annotations are present, dependencytrack/project-id takes precedence. The name lookup calls GET /api/v1/project/latest/{name}, so make sure the proxy allowedMethods permits GET (it does in the example above).