@sap-ux/abap-deploy-config-sub-generator Apache-2.0 36 versions

@sap-ux/abap-deploy-config-sub-generator

npm Repository

Sub generator for ABAP deployment configuration

36

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tqueckkranthie.sapsap_extncrepossap-ospo-admindevinea

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; addition is consistent with SAP org governance, not a compromise signal.	ai	2026/05/27
provenance	publisher-changed	AI (provenance): SAP open-ux-tools migrated to GitHub Actions publishing with SLSA attestation; this is the expected CI/CD pattern for this org.	ai	2026/05/27
dependencies	unvetted-dep:@sap-ux/ui5-config	AI (dependencies): Same SAP org scope; sibling package in the open-ux-tools monorepo.	ai	2026/05/26
dependencies	unvetted-dep:@sap-ux/adp-tooling	AI (dependencies): Same SAP org scope; sibling package in the open-ux-tools monorepo.	ai	2026/05/26
dependencies	unvetted-dep:@sap-ux/feature-toggle	AI (dependencies): Same SAP org scope; sibling package in the open-ux-tools monorepo.	ai	2026/05/26
dependencies	unvetted-dep:@sap-devx/yeoman-ui-types	AI (dependencies): SAP-devx org scope; consistent with SAP tooling ecosystem.	ai	2026/05/26
provenance	no-provenance	AI (provenance): SAP open-ux-tools monorepo does not publish with Sigstore provenance; stable pattern across all versions.	ai	2026/05/26
dependencies	unvetted-dep:@sap-ux/axios-extension	AI (dependencies): Same SAP org scope; sibling package in the open-ux-tools monorepo.	ai	2026/05/26
dependencies	unvetted-dep:@sap-ux/btp-utils	AI (dependencies): Same SAP org scope; sibling package in the open-ux-tools monorepo.	ai	2026/05/26
phantom-deps	phantom-dep:@sap-ux/logger	AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is a stable false positive here.	ai	2026/04/29

Versions (showing 36 of 244)

Version	Deps	Published
0.1.27	11 / 9	2025-06-24
0.1.26	11 / 9	2025-06-23
0.1.25	11 / 9	2025-06-20
0.1.24	11 / 9	2025-06-19
0.1.23	11 / 9	2025-06-19
0.1.22	11 / 9	2025-06-18
0.1.21	11 / 9	2025-06-17
0.1.20	11 / 9	2025-06-16
0.1.19	11 / 9	2025-06-13
0.1.18	11 / 9	2025-06-13
0.1.17	11 / 9	2025-06-11
0.1.16	11 / 9	2025-06-10
0.1.15	11 / 9	2025-06-10
0.1.14	11 / 9	2025-06-09
0.1.13	11 / 9	2025-06-09
0.1.12	11 / 9	2025-06-06
0.1.11	11 / 9	2025-06-05
0.1.10	11 / 9	2025-06-05
0.1.9	11 / 9	2025-06-05
0.1.8	12 / 9	2025-06-04
0.1.7	12 / 9	2025-05-30
0.1.6	12 / 9	2025-05-30
0.1.5	12 / 9	2025-05-28
0.1.4	12 / 9	2025-05-27
0.1.3	12 / 9	2025-05-27
0.1.2	12 / 9	2025-05-23
0.1.1	12 / 9	2025-05-15
0.1.0	12 / 9	2025-05-14
0.0.75	12 / 9	2025-05-13
0.0.74	12 / 9	2025-05-05
0.0.73	12 / 9	2025-05-02
0.0.72	12 / 9	2025-05-02
0.0.71	12 / 9	2025-05-01
0.0.70	12 / 9	2025-04-30
0.0.69	12 / 9	2025-04-30
0.0.68	12 / 9	2025-04-28

v0.1.27

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.

v0.1.26

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.

v0.1.25

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.

v0.1.24

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.

v0.1.23

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.

v0.1.22

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.

v0.1.21

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.

v0.1.20

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.

v0.1.19

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.

v0.1.18

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.

v0.1.17

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.

v0.1.16

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.

v0.1.15

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.

v0.1.14

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.

v0.1.13

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.

v0.1.12

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.

v0.1.11

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.

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

v0.1.9

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.

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

v0.1.7

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.

v0.1.6

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.

v0.1.5

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.

v0.1.4

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.

v0.1.3

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.

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

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

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

v0.0.75

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.

v0.0.74

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.

v0.0.73

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.

v0.0.72

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.

v0.0.71

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.

v0.0.70

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.

v0.0.69

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.

v0.0.68

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.