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

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

npm Repository

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:knex	AI (phantom-deps): knex is used for DB migrations in a Backstage backend plugin; referenced in config/migrations, not direct imports.	ai	2026/05/14
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): Standard Backstage backend plugin pattern; used via DI/config rather than direct import.	ai	2026/05/14
phantom-deps	phantom-dep:@backstage/backend-defaults	AI (phantom-deps): Standard Backstage backend plugin pattern; used via DI/config rather than direct import.	ai	2026/05/14

Versions (showing 22 of 22)

Version	Deps	Published
2.7.6	16 / 6	2026-05-18
2.7.5	16 / 6	2026-05-18
2.7.4	16 / 6	2026-05-12
2.7.3	16 / 6	2026-05-05
2.7.2	16 / 6	2026-05-05
2.7.1	16 / 6	2026-04-28
2.7.0	16 / 6	2026-04-28
2.6.0	16 / 6	2026-04-28
2.5.2	16 / 6	2026-04-23
2.5.1	16 / 6	2026-04-17
2.5.0	16 / 6	2026-04-15
2.4.0	16 / 5	2026-03-04
2.3.5	16 / 5	2026-02-04
2.3.4	16 / 5	2026-02-02
2.3.3	16 / 5	2026-01-31
2.3.2	16 / 5	2026-01-28
2.3.1	16 / 5	2026-01-23
2.3.0	16 / 5	2026-01-16
2.2.0	16 / 5	2025-12-09
2.1.0	16 / 5	2025-11-07
2.0.1	16 / 5	2025-11-06
2.0.0	16 / 5	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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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

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

v2.3.3

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

v2.3.1

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.3.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.2.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.1.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.0.1

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