← Home

@backstage/frontend-dev-utils

Utilities for developing Backstage frontend plugins using the new frontend system.

3
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@backstage/ui AI (dependencies): @backstage/ui is a first-party package from the Backstage monorepo; unvetted status reflects review queue lag, not a security concern. ai
dependencies unvetted-dep:@backstage/plugin-app AI (dependencies): @backstage/plugin-app is a first-party package from the Backstage monorepo; unvetted status reflects review queue lag, not a security concern. ai
dependencies unvetted-dep:@backstage/frontend-defaults AI (dependencies): @backstage/frontend-defaults is a first-party package from the Backstage monorepo; unvetted status reflects review queue lag, not a security concern. ai
dependencies unvetted-dep:@backstage/frontend-plugin-api AI (dependencies): @backstage/frontend-plugin-api is a first-party package from the Backstage monorepo; unvetted status reflects review queue lag, not a security concern. ai
provenance no-provenance AI (provenance): Backstage monorepo packages are not currently published with Sigstore provenance; this is consistent across the ecosystem and not a security risk. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.2 4 / 8
0.1.1 4 / 8
0.1.0 4 / 8

v0.1.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.