@sap-ux/ui5-test-writer
SAP UI5 tests writer
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI is expected for SAP monorepo; SLSA attestation confirms integrity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @sap-ux/preview-middleware is a first-party SAP UX package from the same monorepo; low risk. | ai | |
| provenance | no-provenance | AI (provenance): SAP open-ux-tools monorepo; provenance not configured but package is well-established and low-risk. | ai | |
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): ejs is a declared runtime dep used via EJS template rendering; phantom-dep heuristic misfires here. | ai |
Versions (showing 37 of 147)
| Version | Deps | Published |
|---|---|---|
| 0.7.35 | 7 / 7 | |
| 0.7.34 | 7 / 7 | |
| 0.7.33 | 7 / 7 | |
| 0.7.32 | 7 / 7 | |
| 0.7.31 | 7 / 7 | |
| 0.7.30 | 7 / 7 | |
| 0.7.29 | 7 / 7 | |
| 0.7.28 | 7 / 7 | |
| 0.7.27 | 7 / 7 | |
| 0.7.26 | 7 / 7 | |
| 0.7.25 | 7 / 7 | |
| 0.7.24 | 7 / 7 | |
| 0.7.23 | 7 / 7 | |
| 0.7.22 | 7 / 7 | |
| 0.7.21 | 7 / 7 | |
| 0.7.20 | 7 / 7 | |
| 0.7.19 | 7 / 7 | |
| 0.7.18 | 7 / 7 | |
| 0.7.17 | 7 / 7 | |
| 0.7.16 | 7 / 7 | |
| 0.7.15 | 7 / 7 | |
| 0.7.14 | 7 / 7 | |
| 0.7.13 | 7 / 7 | |
| 0.7.12 | 7 / 5 | |
| 0.7.11 | 7 / 5 | |
| 0.7.10 | 7 / 5 | |
| 0.7.9 | 7 / 5 | |
| 0.7.8 | 7 / 5 | |
| 0.7.7 | 7 / 5 | |
| 0.7.6 | 7 / 5 | |
| 0.7.5 | 7 / 5 | |
| 0.7.4 | 6 / 6 | |
| 0.7.3 | 6 / 6 | |
| 0.7.2 | 6 / 6 | |
| 0.7.1 | 6 / 6 | |
| 0.7.0 | 6 / 6 | |
| 0.6.7 | 6 / 6 |
v0.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.