@backstage/plugin-search-backend-module-explore Apache-2.0 13 versions

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

npm Repository Homepage

A module for the search backend that exports explore modules

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@backstage-community/plugin-explore-common	AI (dependencies): @backstage-community is the official Backstage community org; this dep is expected given the package.json 'moved' field pointing to this community package.	ai	2026/04/27
phantom-deps	phantom-dep:@backstage/config	AI (phantom-deps): @backstage/config is declared for its configSchema (config.d.ts) rather than direct import — standard Backstage pattern; stable false positive for this package.	ai	2026/04/25

Versions (showing 13 of 13)

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

v0.3.14

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

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