← Home

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

npm Repository

A module that subscribes to catalog related events and logs them.

13
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
bogus-package bogus-package AI (bogus-package): Official Backstage monorepo plugin; short README and no keywords are typical of internal monorepo packages, not spam indicators. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Official Backstage monorepo dependency; expected and legitimate for this package. ai
dependencies unvetted-dep:@backstage/plugin-events-node AI (dependencies): Official Backstage monorepo dependency; expected and legitimate for this package. ai
dependencies unvetted-dep:@backstage/plugin-catalog-backend AI (dependencies): Official Backstage monorepo dependency; expected and legitimate for this package. ai

Versions (showing 13 of 13)

Version Deps Published
0.1.22 3 / 3
0.1.21 3 / 3
0.1.20 3 / 3
0.1.19 3 / 3
0.1.18 3 / 3
0.1.17 3 / 3
0.1.16 3 / 3
0.1.15 3 / 3
0.1.14 3 / 3
0.1.13 3 / 3
0.1.12 3 / 3
0.1.11 3 / 3
0.1.10 3 / 3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

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

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

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