← Home

@red-hat-developer-hub/backstage-plugin-theme

npm Repository Homepage
46
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nickboldtbethany.griggskashish_mittaltomaskralrhdh-botschultzp2020

Keywords

backstagerhdhthemeredhat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to rhdh-bot is a Red Hat org-wide CI/CD automation account; consistent with other approved packages from same publisher. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects org publishing cadence, not account takeover; rhdh-bot has 33 approved packages across the same org. ai

Versions (showing 46 of 46)

Version Deps Published
0.15.0 3 / 17
0.14.11 3 / 17
0.14.10 3 / 17
0.14.9 3 / 17
0.14.8 3 / 17
0.14.7 3 / 18
0.14.5 3 / 18
0.14.4 3 / 18
0.14.3 3 / 19
0.14.2 3 / 19
0.14.1 3 / 19
0.14.0 1 / 21
0.13.0 1 / 21
0.12.3 1 / 16
0.12.2 1 / 16
0.12.1 1 / 16
0.12.0 1 / 16
0.11.0 1 / 16
0.10.2 1 / 16
0.10.1 1 / 16
0.10.0 1 / 16
0.9.1 1 / 16
0.9.0 1 / 16
0.8.3 1 / 16
0.8.2 1 / 16
0.8.1 1 / 16
0.8.0 1 / 16
0.7.0 1 / 16
0.6.0 1 / 16
0.5.0 0 / 16
0.4.9 0 / 14
0.4.8 0 / 14
0.4.7 1 / 15
0.4.6 1 / 15
0.4.5 1 / 15
0.4.4 1 / 15
0.4.3 1 / 15
0.4.2 1 / 15
0.4.1 1 / 15
0.4.0 1 / 15
0.3.0 1 / 15
0.2.2 1 / 15
0.2.1 1 / 15
0.2.0 0 / 13
0.1.0 4 / 9
0.0.1 4 / 9

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.14.11

1 finding
LOW No provenance attestation provenance

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

v0.14.10

1 finding
LOW No provenance attestation provenance

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

v0.14.9

1 finding
LOW No provenance attestation provenance

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

v0.14.8

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.9

1 finding
LOW No provenance attestation provenance

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

v0.4.8

1 finding
LOW No provenance attestation provenance

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

v0.4.7

1 finding
LOW No provenance attestation provenance

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

v0.4.6

1 finding
LOW No provenance attestation provenance

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

v0.4.5

1 finding
LOW No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

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