@sap-ux/adp-tooling
Tooling for UI5 adaptation projects
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): ejs is a plausible templating dep for scaffolding tool; no malicious behavior indicated. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher is confirmed by SLSA provenance attestation; stable pattern for this SAP package. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Scaffolding tool; phantom-dep heuristic fires on template/config references, not a real missing import. | ai | |
| phantom-deps | phantom-dep:@sap-devx/yeoman-ui-types | AI (phantom-deps): Type-only dependency used in config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 100 of 562)
| Version | Deps | Published |
|---|---|---|
| 1.0.39 | 26 / 18 | |
| 1.0.37 | 26 / 18 | |
| 1.0.36 | 26 / 18 | |
| 1.0.35 | 26 / 18 | |
| 1.0.34 | 26 / 18 | |
| 1.0.33 | 26 / 18 | |
| 1.0.32 | 26 / 18 | |
| 1.0.31 | 26 / 18 | |
| 1.0.30 | 26 / 18 | |
| 1.0.29 | 26 / 18 | |
| 1.0.28 | 26 / 18 | |
| 1.0.27 | 26 / 18 | |
| 1.0.26 | 26 / 18 | |
| 1.0.25 | 26 / 18 | |
| 1.0.24 | 26 / 18 | |
| 1.0.23 | 26 / 18 | |
| 1.0.22 | 26 / 18 | |
| 1.0.21 | 26 / 18 | |
| 1.0.20 | 26 / 19 | |
| 1.0.19 | 26 / 19 | |
| 1.0.18 | 26 / 19 | |
| 1.0.17 | 26 / 19 | |
| 1.0.16 | 26 / 19 | |
| 1.0.15 | 26 / 19 | |
| 1.0.14 | 26 / 19 | |
| 1.0.13 | 26 / 19 | |
| 1.0.12 | 26 / 19 | |
| 1.0.11 | 26 / 19 | |
| 1.0.10 | 26 / 19 | |
| 1.0.9 | 26 / 19 | |
| 1.0.8 | 26 / 19 | |
| 1.0.7 | 26 / 19 | |
| 1.0.6 | 26 / 19 | |
| 1.0.4 | 26 / 19 | |
| 1.0.3 | 26 / 19 | |
| 1.0.1 | 26 / 19 | |
| 1.0.0 | 26 / 19 | |
| 0.19.11 | 26 / 18 | |
| 0.19.10 | 26 / 18 | |
| 0.19.9 | 26 / 18 | |
| 0.19.7 | 26 / 18 | |
| 0.19.6 | 26 / 18 | |
| 0.19.5 | 26 / 18 | |
| 0.19.3 | 26 / 18 | |
| 0.19.2 | 26 / 18 | |
| 0.19.1 | 26 / 18 | |
| 0.18.130 | 26 / 18 | |
| 0.18.129 | 26 / 18 | |
| 0.18.128 | 26 / 18 | |
| 0.18.126 | 26 / 18 | |
| 0.18.125 | 26 / 18 | |
| 0.18.124 | 26 / 18 | |
| 0.18.123 | 26 / 18 | |
| 0.18.122 | 26 / 18 | |
| 0.18.121 | 26 / 18 | |
| 0.18.120 | 26 / 18 | |
| 0.18.119 | 26 / 18 | |
| 0.18.118 | 26 / 18 | |
| 0.18.117 | 26 / 18 | |
| 0.18.116 | 26 / 18 | |
| 0.18.115 | 26 / 18 | |
| 0.18.114 | 26 / 18 | |
| 0.18.113 | 26 / 18 | |
| 0.18.112 | 26 / 18 | |
| 0.18.111 | 26 / 18 | |
| 0.18.110 | 26 / 18 | |
| 0.18.109 | 26 / 18 | |
| 0.18.108 | 26 / 18 | |
| 0.18.107 | 26 / 18 | |
| 0.18.106 | 26 / 18 | |
| 0.18.105 | 26 / 18 | |
| 0.18.104 | 26 / 18 | |
| 0.18.103 | 26 / 18 | |
| 0.18.102 | 26 / 18 | |
| 0.18.101 | 26 / 18 | |
| 0.18.100 | 26 / 18 | |
| 0.18.99 | 26 / 18 | |
| 0.18.98 | 26 / 18 | |
| 0.18.97 | 26 / 18 | |
| 0.18.96 | 26 / 18 | |
| 0.18.95 | 26 / 18 | |
| 0.18.94 | 26 / 18 | |
| 0.18.93 | 26 / 18 | |
| 0.18.92 | 26 / 18 | |
| 0.18.91 | 26 / 18 | |
| 0.18.90 | 26 / 18 | |
| 0.18.89 | 26 / 18 | |
| 0.18.88 | 26 / 18 | |
| 0.18.86 | 26 / 18 | |
| 0.18.85 | 26 / 18 | |
| 0.18.84 | 26 / 18 | |
| 0.18.83 | 26 / 18 | |
| 0.18.82 | 26 / 18 | |
| 0.18.81 | 26 / 18 | |
| 0.18.80 | 26 / 18 | |
| 0.18.79 | 26 / 18 | |
| 0.18.78 | 26 / 18 | |
| 0.18.77 | 26 / 18 | |
| 0.18.76 | 26 / 18 | |
| 0.18.75 | 26 / 18 |
v1.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.90
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-10, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.18.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.