@backstage/plugin-search-backend-module-catalog Apache-2.0 12 versions

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

npm Repository Homepage

A module for the search backend that exports catalog modules

12

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.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@backstage/config	AI (phantom-deps): First-party Backstage monorepo package; phantom dep pattern is expected in this monorepo ecosystem.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): First-party Backstage monorepo package; phantom dep pattern is expected in this monorepo ecosystem.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-search-common	AI (phantom-deps): First-party Backstage monorepo package; phantom dep pattern is expected in this monorepo ecosystem.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-permission-common	AI (phantom-deps): First-party Backstage monorepo package; phantom dep pattern is expected in this monorepo ecosystem.	ai	2026/04/25

Versions (showing 12 of 12)

Version	Deps	Published
0.3.15	10 / 2	2026-05-19
0.3.14	10 / 2	2026-04-14
0.3.13	10 / 2	2026-03-17
0.3.12	10 / 2	2026-02-17
0.3.11	10 / 2	2025-12-16
0.3.10	10 / 2	2025-11-18
0.3.9	10 / 2	2025-10-14
0.3.8	10 / 2	2025-09-16
0.3.7	10 / 2	2025-08-19
0.3.6	10 / 2	2025-07-15
0.3.5	10 / 2	2025-06-17
0.3.4	10 / 2	2025-05-20

v0.3.15

1 finding

LOW No provenance attestation provenance

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

v0.3.14

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

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

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

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.