@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-jira Apache-2.0 22 versions

@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-jira

npm Repository Homepage

The jira backend module for the scorecard plugin.

22

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

nickboldtbethany.griggskashish_mittaltomaskralrhdh-botschultzp2020

Keywords

backstageplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@backstage/catalog-model	AI (phantom-deps): Backstage catalog-model is referenced in config schema, not direct imports; stable false positive for this plugin.	ai	2026/05/14
phantom-deps	phantom-dep:@backstage/plugin-catalog-node	AI (phantom-deps): Backstage plugin-catalog-node referenced in config files only; expected pattern for Backstage backend modules.	ai	2026/05/14

Versions (showing 22 of 22)

Version	Deps	Published
2.7.6	6 / 3	2026-05-18
2.7.5	6 / 3	2026-05-18
2.7.4	6 / 3	2026-05-12
2.7.3	6 / 3	2026-05-05
2.7.2	6 / 3	2026-05-05
2.7.1	6 / 3	2026-04-28
2.7.0	6 / 3	2026-04-28
2.6.0	6 / 3	2026-04-28
2.5.2	6 / 3	2026-04-23
2.5.1	6 / 3	2026-04-17
2.5.0	6 / 3	2026-04-15
2.4.0	6 / 3	2026-03-04
2.3.5	6 / 3	2026-02-04
2.3.4	6 / 3	2026-02-02
2.3.3	6 / 3	2026-01-31
2.3.2	6 / 3	2026-01-28
2.3.1	6 / 3	2026-01-23
2.3.0	6 / 3	2026-01-16
2.2.0	6 / 3	2025-12-09
2.1.0	6 / 3	2025-11-07
2.0.1	6 / 3	2025-11-06
2.0.0	6 / 3	2025-11-06

v2.7.6

1 finding

LOW No provenance attestation provenance

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

v2.7.5

1 finding

LOW No provenance attestation provenance

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

v2.7.4

1 finding

LOW No provenance attestation provenance

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

v2.7.3

1 finding

LOW No provenance attestation provenance

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

v2.7.2

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

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.

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

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.