@sap-ux/odata-service-inquirer
Prompts module that can prompt users for inputs required for odata service writing
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @sap-devx/yeoman-ui-types is a legitimate SAP DevX package; low risk for this SAP-org package. | ai | |
| dependencies | unvetted-dep:@sap/cf-tools | AI (dependencies): SAP-scoped dependency consistent with this package's ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/edmx-parser | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/nodejs-utils | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/annotation-converter | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/guided-answers-helper | AI (dependencies): Same SAP UX org scope; expected transitive dependency. | ai | |
| dependencies | unvetted-dep:@sap-devx/yeoman-ui-types | AI (dependencies): SAP DevX org scope; newly added but consistent with SAP tooling ecosystem. | ai | |
| dependencies | unvetted-dep:circular-reference-remover | AI (dependencies): Utility dependency; no malicious indicators, stable pattern. | ai | |
| phantom-deps | phantom-dep:os-name | AI (phantom-deps): os-name is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sap-ux/guided-answers-helper | AI (phantom-deps): Declared runtime dep in same SAP org scope; phantom-dep heuristic false positive. | ai |
Versions (showing 100 of 205)
| Version | Deps | Published |
|---|---|---|
| 2.11.1 | 21 / 12 | |
| 2.11.0 | 21 / 12 | |
| 2.10.0 | 21 / 12 | |
| 2.9.14 | 21 / 12 | |
| 2.9.13 | 21 / 12 | |
| 2.9.12 | 21 / 12 | |
| 2.9.11 | 21 / 12 | |
| 2.9.10 | 21 / 12 | |
| 2.9.9 | 21 / 12 | |
| 2.9.8 | 21 / 12 | |
| 2.9.7 | 21 / 12 | |
| 2.9.5 | 21 / 12 | |
| 2.9.4 | 21 / 12 | |
| 2.9.3 | 21 / 12 | |
| 2.9.2 | 21 / 12 | |
| 2.9.1 | 21 / 12 | |
| 2.9.0 | 21 / 12 | |
| 2.8.13 | 21 / 12 | |
| 2.8.12 | 21 / 12 | |
| 2.8.11 | 21 / 12 | |
| 2.8.10 | 21 / 12 | |
| 2.8.9 | 21 / 12 | |
| 2.8.7 | 21 / 12 | |
| 2.8.6 | 21 / 12 | |
| 2.8.5 | 21 / 12 | |
| 2.8.4 | 21 / 12 | |
| 2.8.3 | 21 / 12 | |
| 2.8.2 | 21 / 12 | |
| 2.8.1 | 21 / 12 | |
| 2.8.0 | 21 / 12 | |
| 2.7.3 | 21 / 12 | |
| 2.7.2 | 21 / 12 | |
| 2.7.1 | 21 / 12 | |
| 2.7.0 | 21 / 12 | |
| 2.6.1 | 21 / 12 | |
| 2.6.0 | 21 / 12 | |
| 2.5.33 | 21 / 12 | |
| 2.5.32 | 21 / 12 | |
| 2.5.31 | 21 / 12 | |
| 2.5.30 | 21 / 12 | |
| 2.5.29 | 21 / 12 | |
| 2.5.28 | 20 / 12 | |
| 2.5.27 | 20 / 12 | |
| 2.5.26 | 20 / 12 | |
| 2.5.25 | 20 / 12 | |
| 2.5.24 | 20 / 12 | |
| 2.5.23 | 20 / 12 | |
| 2.5.22 | 20 / 12 | |
| 2.5.21 | 20 / 12 | |
| 2.5.20 | 20 / 12 | |
| 2.5.19 | 20 / 12 | |
| 2.5.18 | 20 / 12 | |
| 2.5.17 | 20 / 12 | |
| 2.5.16 | 20 / 12 | |
| 2.5.15 | 20 / 12 | |
| 2.5.14 | 20 / 12 | |
| 2.5.13 | 20 / 12 | |
| 2.5.12 | 20 / 12 | |
| 2.5.11 | 20 / 12 | |
| 2.5.10 | 20 / 12 | |
| 2.5.9 | 20 / 12 | |
| 2.5.8 | 20 / 12 | |
| 2.5.7 | 20 / 12 | |
| 2.5.6 | 20 / 12 | |
| 2.5.5 | 20 / 12 | |
| 2.5.4 | 20 / 12 | |
| 2.5.3 | 20 / 12 | |
| 2.5.2 | 20 / 12 | |
| 2.5.1 | 20 / 12 | |
| 2.5.0 | 20 / 12 | |
| 2.4.23 | 20 / 12 | |
| 2.4.22 | 20 / 12 | |
| 2.4.21 | 20 / 12 | |
| 2.4.20 | 20 / 12 | |
| 2.4.19 | 20 / 12 | |
| 2.4.18 | 20 / 12 | |
| 2.4.17 | 20 / 12 | |
| 2.4.16 | 20 / 12 | |
| 2.4.15 | 20 / 12 | |
| 2.4.14 | 19 / 12 | |
| 2.4.13 | 19 / 12 | |
| 2.4.12 | 19 / 12 | |
| 2.4.11 | 19 / 12 | |
| 2.4.10 | 19 / 12 | |
| 2.4.9 | 19 / 12 | |
| 2.4.8 | 19 / 12 | |
| 2.4.7 | 19 / 12 | |
| 2.4.6 | 19 / 12 | |
| 2.4.5 | 19 / 12 | |
| 2.4.4 | 19 / 12 | |
| 2.4.3 | 19 / 12 | |
| 2.4.2 | 19 / 12 | |
| 2.4.1 | 19 / 12 | |
| 2.4.0 | 19 / 12 | |
| 2.3.15 | 19 / 12 | |
| 2.3.14 | 19 / 12 | |
| 2.3.13 | 19 / 12 | |
| 2.3.12 | 19 / 12 | |
| 2.3.11 | 19 / 12 | |
| 2.3.10 | 19 / 12 |
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.