@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 |
|---|---|---|
| 0.15.30 | 23 / 16 | |
| 0.15.29 | 23 / 16 | |
| 0.15.28 | 23 / 16 | |
| 0.15.27 | 23 / 16 | |
| 0.15.26 | 23 / 16 | |
| 0.15.25 | 23 / 16 | |
| 0.15.24 | 23 / 16 | |
| 0.15.23 | 23 / 16 | |
| 0.15.22 | 23 / 16 | |
| 0.15.21 | 23 / 16 | |
| 0.15.20 | 23 / 16 | |
| 0.15.19 | 23 / 16 | |
| 0.15.18 | 23 / 16 | |
| 0.15.17 | 23 / 16 | |
| 0.15.16 | 23 / 16 | |
| 0.15.15 | 23 / 16 | |
| 0.15.14 | 23 / 16 | |
| 0.15.13 | 23 / 16 | |
| 0.15.12 | 23 / 16 | |
| 0.15.11 | 23 / 16 | |
| 0.15.10 | 23 / 16 | |
| 0.15.9 | 23 / 16 | |
| 0.15.8 | 23 / 16 | |
| 0.15.7 | 23 / 16 | |
| 0.15.6 | 23 / 16 | |
| 0.15.5 | 23 / 16 | |
| 0.15.4 | 23 / 16 | |
| 0.15.3 | 23 / 16 | |
| 0.15.2 | 23 / 16 | |
| 0.15.1 | 23 / 16 | |
| 0.15.0 | 23 / 16 | |
| 0.14.44 | 23 / 16 | |
| 0.14.43 | 23 / 16 | |
| 0.14.42 | 23 / 16 | |
| 0.14.41 | 23 / 16 | |
| 0.14.40 | 23 / 16 | |
| 0.14.39 | 23 / 16 | |
| 0.14.38 | 23 / 16 | |
| 0.14.37 | 23 / 16 | |
| 0.14.36 | 23 / 16 | |
| 0.14.35 | 23 / 16 | |
| 0.14.34 | 23 / 16 | |
| 0.14.33 | 23 / 16 | |
| 0.14.32 | 23 / 16 | |
| 0.14.31 | 23 / 16 | |
| 0.14.30 | 23 / 16 | |
| 0.14.29 | 23 / 16 | |
| 0.14.28 | 22 / 16 | |
| 0.14.27 | 22 / 16 | |
| 0.14.26 | 22 / 16 | |
| 0.14.25 | 22 / 16 | |
| 0.14.24 | 22 / 16 | |
| 0.14.23 | 22 / 16 | |
| 0.14.22 | 22 / 16 | |
| 0.14.21 | 22 / 16 | |
| 0.14.20 | 22 / 16 | |
| 0.14.19 | 22 / 16 | |
| 0.14.18 | 22 / 16 | |
| 0.14.17 | 22 / 16 | |
| 0.14.16 | 21 / 16 | |
| 0.14.15 | 21 / 16 | |
| 0.14.14 | 21 / 16 | |
| 0.14.13 | 21 / 16 | |
| 0.14.12 | 21 / 16 | |
| 0.14.11 | 21 / 16 | |
| 0.14.10 | 21 / 16 | |
| 0.14.9 | 21 / 16 | |
| 0.14.8 | 21 / 16 | |
| 0.14.7 | 21 / 16 | |
| 0.14.6 | 21 / 16 | |
| 0.14.5 | 21 / 16 | |
| 0.14.4 | 21 / 16 | |
| 0.14.3 | 21 / 16 | |
| 0.14.2 | 21 / 16 | |
| 0.14.1 | 21 / 16 | |
| 0.14.0 | 21 / 16 | |
| 0.13.45 | 21 / 16 | |
| 0.13.44 | 21 / 16 | |
| 0.13.43 | 21 / 16 | |
| 0.13.42 | 21 / 16 | |
| 0.13.41 | 21 / 16 | |
| 0.13.40 | 21 / 16 | |
| 0.13.39 | 21 / 16 | |
| 0.13.38 | 21 / 16 | |
| 0.13.37 | 21 / 16 | |
| 0.13.36 | 21 / 16 | |
| 0.13.35 | 21 / 16 | |
| 0.13.34 | 21 / 16 | |
| 0.13.33 | 21 / 16 | |
| 0.13.32 | 21 / 16 | |
| 0.13.31 | 21 / 16 | |
| 0.13.30 | 21 / 16 | |
| 0.13.29 | 21 / 16 | |
| 0.13.28 | 21 / 16 | |
| 0.13.27 | 21 / 16 | |
| 0.13.26 | 21 / 16 | |
| 0.13.25 | 21 / 16 | |
| 0.13.24 | 21 / 16 | |
| 0.13.22 | 21 / 16 | |
| 0.13.21 | 21 / 16 |
v0.15.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.