← Home

@backstage/plugin-app-visualizer

npm Repository

Visualizes the Backstage app structure

15
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@backstage/core-plugin-api AI (phantom-deps): Same-org dependency declared in package.json; common pattern in Backstage plugin packages where APIs are consumed transitively. ai
bogus-package bogus-package AI (bogus-package): Backstage monorepo sub-packages commonly have minimal READMEs and no keywords; this is a structural pattern, not spam. ai
dependencies unvetted-dep:@remixicon/react AI (dependencies): @remixicon/react is a well-known legitimate icon library; its use in a UI visualization plugin is expected and benign. ai

Versions (showing 15 of 15)

Version Deps Published
0.2.4 6 / 6
0.2.3 6 / 6
0.2.2 6 / 6
0.2.1 6 / 6
0.2.0 6 / 6
0.1.28 6 / 6
0.1.27 6 / 6
0.1.26 6 / 6
0.1.25 6 / 6
0.1.24 5 / 6
0.1.23 5 / 6
0.1.22 5 / 6
0.1.21 5 / 6
0.1.20 5 / 6
0.1.19 5 / 6

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

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.

v0.1.28

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.

v0.1.24

1 finding
LOW No provenance attestation provenance

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

v0.1.23

1 finding
LOW No provenance attestation provenance

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

v0.1.22

1 finding
LOW No provenance attestation provenance

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

v0.1.21

1 finding
LOW No provenance attestation provenance

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

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

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.