@cubejs-client/ngx MIT 54 versions

@cubejs-client/ngx

npm Repository Homepage

Cube.js client for Angular

54

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cubedevincstatsbotkeydunovmaxim_cube

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/esm2015/src/client.js	AI (source-diff): Standard ng-packagr ESM2015 build output; long lines from bundling, not obfuscation.	ai	2026/05/08
bogus-package	bogus-package	AI (bogus-package): Established Angular client library; README quality signals are not meaningful for this package.	ai	2026/05/08
source-diff	obfuscated-file:dist/esm2015/src/query-builder/query.js	AI (source-diff): Standard ng-packagr ESM2015 build output; long lines from bundling, not obfuscation.	ai	2026/05/08
source-diff	obfuscated-file:dist/esm2015/src/query-builder/query-members.js	AI (source-diff): Standard ng-packagr ESM2015 build output; long lines from bundling, not obfuscation.	ai	2026/05/08
source-diff	obfuscated-file:dist/esm2015/src/query-builder/query-builder.service.js	AI (source-diff): Standard ng-packagr ESM2015 build output; long lines from bundling, not obfuscation.	ai	2026/05/08
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions CI publishing is documented by SLSA attestation; consistent across cube-js monorepo releases.	ai	2026/05/08
typosquat	typosquat.levenshtein:next	AI (typosquat): ngx is the Angular ecosystem suffix; @cubejs-client/ngx is the legitimate Cube.js Angular client, not a typosquat.	ai	2026/05/05
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package.	ai	2026/05/05
typosquat	typosquat.levenshtein:pg	AI (typosquat): Same rationale — scoped package under @cubejs-client org, not a pg typosquat.	ai	2026/05/05
typosquat	typosquat.levenshtein:knex	AI (typosquat): Same rationale — scoped package under @cubejs-client org, not a knex typosquat.	ai	2026/05/05
typosquat	typosquat.levenshtein:nuxt	AI (typosquat): Same rationale — scoped package under @cubejs-client org, not a nuxt typosquat.	ai	2026/05/05

Versions (showing 54 of 159)

Version	Deps	Published
1.3.62	2 / 0	2025-08-29
1.3.61	2 / 0	2025-08-28
1.3.60	2 / 0	2025-08-28
1.3.59	2 / 0	2025-08-26
1.3.58	2 / 0	2025-08-25
1.3.57	2 / 0	2025-08-22
1.3.56	2 / 0	2025-08-21
1.3.55	2 / 0	2025-08-19
1.3.54	2 / 0	2025-08-16
1.3.53	2 / 0	2025-08-15
1.3.52	2 / 0	2025-08-14
1.3.51	2 / 0	2025-08-14
1.3.50	2 / 0	2025-08-13
1.3.49	2 / 0	2025-08-12
1.3.48	2 / 0	2025-08-09
1.3.47	2 / 0	2025-08-04
1.3.46	2 / 0	2025-07-31
1.3.45	2 / 0	2025-07-29
1.3.44	2 / 0	2025-07-28
1.3.43	2 / 0	2025-07-24
1.3.42	2 / 0	2025-07-23
1.3.41	2 / 0	2025-07-22
1.3.40	2 / 0	2025-07-20
1.3.39	2 / 0	2025-07-17
1.3.38	2 / 0	2025-07-16
1.3.37	2 / 0	2025-07-14
1.3.36	2 / 0	2025-07-10
1.3.35	2 / 0	2025-07-09
1.3.34	2 / 0	2025-07-04
1.3.33	2 / 0	2025-07-03
1.3.32	2 / 0	2025-07-03
1.3.31	2 / 0	2025-07-02
1.3.30	2 / 0	2025-07-01
1.3.29	2 / 0	2025-07-01
1.3.28	2 / 0	2025-06-30
1.3.27	2 / 0	2025-06-30
1.3.26	2 / 0	2025-06-25
1.3.25	2 / 0	2025-06-24
1.3.24	2 / 0	2025-06-24
1.3.23	2 / 0	2025-06-19
1.3.22	2 / 0	2025-06-18
1.3.21	2 / 0	2025-06-10
1.3.20	2 / 0	2025-06-06
1.3.19	2 / 0	2025-06-02
1.3.18	2 / 0	2025-05-27
1.3.17	2 / 0	2025-05-22
1.3.16	2 / 0	2025-05-19
1.3.15	2 / 0	2025-05-15
1.3.14	2 / 0	2025-05-13
1.3.13	2 / 0	2025-05-12
1.3.12	2 / 0	2025-05-08
1.3.11	2 / 0	2025-05-05
1.0.14	2 / 9	2025-12-16
1.0.13	2 / 9	2025-12-11

v1.3.62

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.3.61

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.3.60

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.3.59

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.3.58

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.3.57

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.3.56

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.3.55

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.3.54

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.3.53

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.3.52

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.3.51

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.3.50

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.3.49

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.3.48

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.3.47

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.3.46

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.3.45

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.3.44

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.3.43

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.3.42

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.3.41

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.3.40

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.3.39

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.3.38

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.3.37

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.3.36

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.3.35

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.3.34

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.3.33

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.3.32

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.3.31

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.3.30

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.3.29

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.3.28

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.3.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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v1.0.14

6 findings

HIGH Publisher changed: statsbot → GitHub Actions (on 2025-12-16) provenance

This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/esm2015/src/client.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: dist/esm2015/src/query-builder/query-builder.service.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: dist/esm2015/src/query-builder/query-members.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: dist/esm2015/src/query-builder/query.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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.13

6 findings

HIGH Publisher changed: statsbot → GitHub Actions (on 2025-12-11) provenance

This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/esm2015/src/client.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: dist/esm2015/src/query-builder/query-builder.service.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: dist/esm2015/src/query-builder/query-members.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: dist/esm2015/src/query-builder/query.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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.