@sap-ux/backend-proxy-middleware
SAP backend proxy middleware
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): SAP org migrated publishing to GitHub Actions CI/CD; SLSA attestation confirms legitimate pipeline origin. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): SAP monorepo sibling package; co-released with this package from SAP/open-ux-tools. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): SAP monorepo sibling package; co-released with this package from SAP/open-ux-tools. | ai |
Versions (showing 62 of 162)
| Version | Deps | Published |
|---|---|---|
| 0.9.2 | 11 / 9 | |
| 0.9.1 | 11 / 9 | |
| 0.9.0 | 11 / 9 | |
| 0.8.44 | 11 / 9 | |
| 0.8.43 | 11 / 9 | |
| 0.8.42 | 11 / 9 | |
| 0.8.41 | 11 / 9 | |
| 0.8.40 | 11 / 9 | |
| 0.8.39 | 11 / 9 | |
| 0.8.38 | 11 / 9 | |
| 0.8.37 | 11 / 9 | |
| 0.8.36 | 11 / 9 | |
| 0.8.35 | 11 / 9 | |
| 0.8.34 | 11 / 9 | |
| 0.8.33 | 11 / 9 | |
| 0.8.32 | 11 / 9 | |
| 0.8.31 | 11 / 9 | |
| 0.8.30 | 11 / 9 | |
| 0.8.29 | 11 / 9 | |
| 0.8.28 | 11 / 9 | |
| 0.8.27 | 11 / 9 | |
| 0.8.26 | 11 / 9 | |
| 0.8.25 | 11 / 9 | |
| 0.8.24 | 11 / 9 | |
| 0.8.22 | 11 / 9 | |
| 0.8.21 | 11 / 9 | |
| 0.8.20 | 11 / 9 | |
| 0.8.19 | 11 / 9 | |
| 0.8.18 | 11 / 9 | |
| 0.8.17 | 11 / 9 | |
| 0.8.16 | 11 / 9 | |
| 0.8.15 | 11 / 9 | |
| 0.8.14 | 11 / 9 | |
| 0.8.13 | 11 / 9 | |
| 0.8.12 | 11 / 9 | |
| 0.8.11 | 11 / 9 | |
| 0.8.10 | 11 / 9 | |
| 0.8.9 | 11 / 9 | |
| 0.8.8 | 11 / 9 | |
| 0.8.7 | 11 / 9 | |
| 0.8.5 | 11 / 9 | |
| 0.8.4 | 11 / 9 | |
| 0.8.3 | 11 / 9 | |
| 0.8.2 | 11 / 9 | |
| 0.8.1 | 11 / 9 | |
| 0.7.41 | 11 / 9 | |
| 0.7.40 | 11 / 9 | |
| 0.7.39 | 11 / 9 | |
| 0.7.38 | 11 / 9 | |
| 0.7.37 | 11 / 9 | |
| 0.7.36 | 11 / 9 | |
| 0.7.35 | 11 / 9 | |
| 0.7.34 | 11 / 9 | |
| 0.7.33 | 11 / 9 | |
| 0.7.32 | 11 / 9 | |
| 0.7.31 | 11 / 9 | |
| 0.7.30 | 11 / 9 | |
| 0.7.29 | 11 / 9 | |
| 0.7.28 | 11 / 9 | |
| 0.7.27 | 11 / 9 | |
| 0.7.26 | 11 / 9 | |
| 0.7.25 | 11 / 9 |
v0.8.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.