← Home

@backstage/plugin-catalog-backend-module-unprocessed

Backstage Catalog module to view unprocessed entities

7
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
provenance no-provenance AI (provenance): Backstage monorepo packages are published via automated tooling without Sigstore provenance; this is consistent across all @backstage/* releases. ai
phantom-deps phantom-dep:@backstage/catalog-model AI (phantom-deps): Same-org monorepo package; declared for type resolution/peer usage in Backstage plugin architecture, not a phantom dep concern. ai
phantom-deps phantom-dep:@backstage/plugin-auth-node AI (phantom-deps): Same-org monorepo package; declared for type resolution/peer usage in Backstage plugin architecture, not a phantom dep concern. ai
phantom-deps phantom-dep:@backstage/plugin-catalog-node AI (phantom-deps): Same-org monorepo package; declared for type resolution/peer usage in Backstage plugin architecture, not a phantom dep concern. ai
phantom-deps phantom-dep:knex AI (phantom-deps): knex is referenced in config files for database configuration, a standard Backstage backend pattern; not a malicious phantom dep. ai

Versions (showing 7 of 7)

Version Deps Published
0.6.12 9 / 7
0.6.11 9 / 7
0.6.10 9 / 2
0.6.9 9 / 2
0.6.8 9 / 2
0.6.7 9 / 2
0.6.6 9 / 2

v0.6.12

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.6.10

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.