@sapui5/sap.fe.test — Greenflagged

SAPUI5 Library sap.fe.test

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sapnaassap_extncrepossap-ospo-admin

Keywords

sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:src/sap/fe/test/AppStateAdapter.js	AI (source-diff): SAP-copyrighted transpiled SAPUI5 source; long lines are Babel output, not obfuscation.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/api/CollaborationAPI.js	AI (source-diff): Long lines from SAP UI5 sap.ui.define dependency arrays; readable, commented SAP-copyright code, not obfuscation.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/CollaborationClient.js	AI (source-diff): Same pattern: SAP UI5 module definition with long import list; fully readable source.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/internal/ConsoleErrorChecker.js	AI (source-diff): Readable SAP-copyright source; long lines from UI5 define pattern.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/FeMocks.js	AI (source-diff): Readable SAP-copyright test mock helper; long lines from UI5 define pattern.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/JestFlexibilityHelper.js	AI (source-diff): Readable SAP-copyright Jest helper; long lines from UI5 define pattern.	ai	2026/05/02
source-diff	obfuscated-file:src/sap/fe/test/UI5MockHelper.js	AI (source-diff): Readable SAP-copyright mock helper; long lines from UI5 define dependency array.	ai	2026/05/02

Versions (showing 51 of 86)

View all versions

Version	Deps	Published
1.148.1	0 / 0	2026-05-28
1.148.0	0 / 0	2026-05-14
1.147.0	0 / 0	2026-04-16
1.146.0	0 / 0	2026-03-19
1.145.3	0 / 0	2026-05-27
1.145.2	0 / 0	2026-04-29
1.145.1	0 / 0	2026-04-03
1.145.0	0 / 0	2026-02-19
1.144.0	0 / 0	2026-01-26
1.143.0	0 / 0	2025-11-27
1.142.11	0 / 0	2026-05-14
1.142.10	0 / 0	2026-04-23
1.142.9	0 / 0	2026-04-15
1.142.8	0 / 0	2026-04-03
1.142.7	0 / 0	2026-03-11
1.142.6	0 / 0	2026-02-11
1.142.5	0 / 0	2026-01-28
1.142.3	0 / 0	2026-01-26
1.142.2	0 / 0	2026-01-07
1.142.1	0 / 0	2025-12-12
1.142.0	0 / 0	2025-10-31
1.141.2	0 / 0	2025-11-07
1.141.1	0 / 0	2025-10-10
1.141.0	0 / 0	2025-10-02
1.140.0	0 / 0	2025-09-04
1.139.4	0 / 0	2025-10-29
1.139.1	0 / 0	2025-10-08
1.139.0	0 / 0	2025-08-07
1.138.0	0 / 0	2025-07-10
1.136.18	0 / 0	2026-05-13
1.136.17	0 / 0	2026-04-16
1.136.16	0 / 0	2026-03-25
1.136.15	0 / 0	2026-02-25
1.136.13	0 / 0	2026-01-16
1.136.12	0 / 0	2025-12-19
1.136.11	0 / 0	2025-11-26
1.136.10	0 / 0	2025-10-29
1.136.9	0 / 0	2025-10-01
1.136.8	0 / 0	2025-09-03
1.136.7	0 / 0	2025-08-20
1.136.6	0 / 0	2025-08-13
1.136.5	0 / 0	2025-08-04
1.136.3	0 / 0	2025-07-30
1.136.2	0 / 0	2025-07-09
1.136.1	0 / 0	2025-06-18
1.136.0	0 / 0	2025-05-15
1.133.4	0 / 0	2025-05-14
1.133.3	0 / 0	2025-05-07
1.133.2	0 / 0	2025-05-01
1.130.11	0 / 0	2025-06-04
1.130.10	0 / 0	2025-05-01

v1.148.1

1 finding

LOW No provenance attestation provenance

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

v1.148.0

1 finding

LOW No provenance attestation provenance

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

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

v1.146.0

1 finding

LOW No provenance attestation provenance

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

v1.145.3

1 finding

LOW No provenance attestation provenance

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

v1.145.2

1 finding

LOW No provenance attestation provenance

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

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

v1.145.0

1 finding

LOW No provenance attestation provenance

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

v1.144.0

1 finding

LOW No provenance attestation provenance

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

v1.143.0

1 finding

LOW No provenance attestation provenance

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

v1.142.11

1 finding

LOW No provenance attestation provenance

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

v1.142.10

1 finding

LOW No provenance attestation provenance

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

v1.142.9

8 findings

HIGH New obfuscated file: src/sap/fe/test/AppStateAdapter.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/api/CollaborationAPI.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/CollaborationClient.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/internal/ConsoleErrorChecker.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/FeMocks.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/JestFlexibilityHelper.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: src/sap/fe/test/UI5MockHelper.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.142.8

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.

v1.142.7

1 finding

LOW No provenance attestation provenance

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

v1.142.6

1 finding

LOW No provenance attestation provenance

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

v1.142.5

1 finding

LOW No provenance attestation provenance

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

v1.142.3

1 finding

LOW No provenance attestation provenance

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

v1.142.2

1 finding

LOW No provenance attestation provenance

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

v1.142.1

1 finding

LOW No provenance attestation provenance

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

v1.142.0

1 finding

LOW No provenance attestation provenance

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

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

v1.141.1

1 finding

LOW No provenance attestation provenance

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

v1.141.0

1 finding

LOW No provenance attestation provenance

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

v1.140.0

1 finding

LOW No provenance attestation provenance

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

v1.139.4

1 finding

LOW No provenance attestation provenance

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

v1.139.1

1 finding

LOW No provenance attestation provenance

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

v1.139.0

1 finding

LOW No provenance attestation provenance

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

v1.138.0

1 finding

LOW No provenance attestation provenance

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

v1.136.18

1 finding

LOW No provenance attestation provenance

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

v1.136.17

1 finding

LOW No provenance attestation provenance

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

v1.136.16

1 finding

LOW No provenance attestation provenance

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

v1.136.15

1 finding

LOW No provenance attestation provenance

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

v1.136.13

1 finding

LOW No provenance attestation provenance

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

v1.136.12

1 finding

LOW No provenance attestation provenance

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

v1.136.11

1 finding

LOW No provenance attestation provenance

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

v1.136.10

1 finding

LOW No provenance attestation provenance

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

v1.136.9

1 finding

LOW No provenance attestation provenance

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

v1.136.8

1 finding

LOW No provenance attestation provenance

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

v1.136.7

1 finding

LOW No provenance attestation provenance

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

v1.136.6

1 finding

LOW No provenance attestation provenance

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

v1.136.5

1 finding

LOW No provenance attestation provenance

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

v1.136.3

1 finding

LOW No provenance attestation provenance

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

v1.136.2

1 finding

LOW No provenance attestation provenance

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

v1.136.1

1 finding

LOW No provenance attestation provenance

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

v1.136.0

1 finding

LOW No provenance attestation provenance

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

v1.133.4

1 finding

LOW No provenance attestation provenance

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

v1.133.3

1 finding

LOW No provenance attestation provenance

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

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

v1.130.11

1 finding

LOW No provenance attestation provenance

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

v1.130.10

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.