@yuuvis/client-framework MIT 48 versions

@yuuvis/client-framework

npm

Component library for creating applications facing a yuuvis® MOMENTUM backend.

48

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

optimal-systems-npmeo-sdk-npm

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@ngrx/signals	AI (dependencies): @ngrx/signals is the official NgRx signals library; stable false positive for this Angular framework package.	ai	2026/05/02
phantom-deps	phantom-dep:angular-split	AI (phantom-deps): angular-split is a declared runtime dep used via config/template references; false positive for this package.	ai	2026/05/02
semgrep	semgrep:new-function-constructor	AI (semgrep): Used in object-form template engine to compile form scripts with sourceURL; stable pattern across versions.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Corporate scoped package with 156 versions; sparse metadata is consistent across all releases.	ai	2026/04/29
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a well-known Angular/TypeScript implicit runtime dependency.	ai	2026/04/29
phantom-deps	phantom-dep:@ngrx/signals	AI (phantom-deps): Referenced in config files as documented; stable false positive for this package.	ai	2026/04/29

Versions (showing 48 of 48)

Version	Deps	Published
3.6.0	7 / 0	2026-06-05
3.5.0	7 / 0	2026-06-02
3.4.2	7 / 0	2026-05-28
3.4.1	7 / 0	2026-05-27
3.4.0	7 / 0	2026-05-27
3.3.0	7 / 0	2026-05-20
3.2.2	7 / 0	2026-05-15
3.2.1	7 / 0	2026-05-13
3.2.0	7 / 0	2026-05-12
3.1.0	7 / 0	2026-05-11
3.0.1	7 / 0	2026-05-05
3.0.0	7 / 0	2026-04-30
2.21.1	7 / 0	2026-05-05
2.21.0	7 / 0	2026-04-29
2.20.1	7 / 0	2026-04-14
2.20.0	7 / 0	2026-04-10
2.19.0	7 / 0	2026-04-09
2.18.0	7 / 0	2026-04-01
2.17.0	7 / 0	2026-03-31
2.16.0	7 / 0	2026-03-30
2.3.31	6 / 0	2025-12-02
2.3.30	6 / 0	2025-12-01
2.3.29	6 / 0	2025-11-27
2.3.28	6 / 0	2025-11-27
2.3.27	6 / 0	2025-11-26
2.3.26	6 / 0	2025-11-26
2.3.25	6 / 0	2025-11-24
2.3.24	6 / 0	2025-11-19
2.3.23	6 / 0	2025-11-19
2.3.22	6 / 0	2025-11-18
2.3.21	6 / 0	2025-11-18
2.3.20	6 / 0	2025-11-18
2.3.19	6 / 0	2025-11-16
2.3.18	6 / 0	2025-11-14
2.3.17	6 / 0	2025-11-14
2.3.16	6 / 0	2025-11-12
2.0.11	6 / 0	2025-06-17
2.0.10	6 / 0	2025-06-16
2.0.9	6 / 0	2025-06-16
2.0.8	6 / 0	2025-06-16
2.0.7	6 / 0	2025-06-11
2.0.6	6 / 0	2025-06-11
2.0.5	7 / 0	2025-06-06
2.0.4	7 / 0	2025-05-28
2.0.3	7 / 0	2025-05-26
2.0.2	7 / 0	2025-05-26
2.0.1	7 / 0	2025-05-23
2.0.0	7 / 0	2025-05-22

v3.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.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.

v2.16.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.

v2.3.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

v2.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.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.

v2.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.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.

v2.0.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.

v2.0.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.