@red-hat-developer-hub/e2e-test-utils
Test utilities for RHDH E2E tests
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Bot-published Red Hat package; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal test utility; sparse README and small entry point are expected for this package type. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is used via config files (prettier:check script), not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is used via tsc in build scripts, not direct import; stable false positive. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 19 / 11 | |
| 1.1.45 | 19 / 11 | |
| 1.1.44 | 19 / 11 | |
| 1.1.43 | 19 / 11 | |
| 1.1.42 | 19 / 11 | |
| 1.1.41 | 19 / 11 | |
| 1.1.40 | 19 / 11 | |
| 1.1.39 | 19 / 11 | |
| 1.1.38 | 19 / 11 | |
| 1.1.37 | 19 / 11 | |
| 1.1.36 | 19 / 11 | |
| 1.1.35 | 19 / 11 | |
| 1.1.34 | 19 / 11 | |
| 1.1.33 | 19 / 11 | |
| 1.1.32 | 18 / 11 | |
| 1.1.31 | 18 / 11 | |
| 1.1.30 | 18 / 11 | |
| 1.1.29 | 18 / 11 | |
| 1.1.28 | 18 / 11 | |
| 1.1.27 | 18 / 11 | |
| 1.1.26 | 18 / 11 | |
| 1.1.25 | 18 / 11 | |
| 1.1.24 | 18 / 11 | |
| 1.1.23 | 18 / 11 | |
| 1.1.22 | 18 / 11 | |
| 1.1.21 | 18 / 11 | |
| 1.1.20 | 18 / 11 | |
| 1.1.19 | 18 / 11 | |
| 1.1.18 | 18 / 11 | |
| 1.1.17 | 18 / 8 | |
| 1.1.16 | 18 / 8 | |
| 1.1.15 | 18 / 8 | |
| 1.1.14 | 17 / 8 | |
| 1.1.13 | 16 / 7 | |
| 1.1.12 | 16 / 7 | |
| 1.1.11 | 16 / 7 | |
| 1.1.10 | 16 / 7 |
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.