@yuuvis/client-core
`@yuuvis/client-core` library provides a set of services to interact with a yuuvis® MOMENTUM backend.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Active library with frequent releases; large file additions are expected for feature releases, not indicative of injected code. | ai | |
| dependencies | unvetted-dep:ngx-device-detector | AI (dependencies): ngx-device-detector is a well-known Angular device detection library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ngx-pwa/local-storage | AI (dependencies): @ngx-pwa/local-storage is a well-known Angular local storage library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 157 versions; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 139)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.4.2 | 4 / 0 | |
| 3.4.1 | 4 / 0 | |
| 3.4.0 | 4 / 0 | |
| 3.3.0 | 4 / 0 | |
| 3.2.2 | 4 / 0 | |
| 3.2.1 | 4 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.21.1 | 4 / 0 | |
| 2.21.0 | 4 / 0 | |
| 2.20.1 | 4 / 0 | |
| 2.20.0 | 4 / 0 | |
| 2.18.0 | 4 / 0 | |
| 2.17.0 | 4 / 0 | |
| 2.16.0 | 4 / 0 | |
| 2.15.0 | 4 / 0 | |
| 2.14.0 | 4 / 0 | |
| 2.13.0 | 4 / 0 | |
| 2.12.4 | 4 / 0 | |
| 2.12.3 | 4 / 0 | |
| 2.12.2 | 4 / 0 | |
| 2.12.1 | 4 / 0 | |
| 2.12.0 | 4 / 0 | |
| 2.11.3 | 4 / 0 | |
| 2.11.2 | 4 / 0 | |
| 2.11.1 | 4 / 0 | |
| 2.11.0 | 4 / 0 | |
| 2.10.3 | 4 / 0 | |
| 2.10.2 | 4 / 0 | |
| 2.10.1 | 4 / 0 | |
| 2.10.0 | 4 / 0 | |
| 2.9.2 | 4 / 0 | |
| 2.9.1 | 4 / 0 | |
| 2.9.0 | 4 / 0 | |
| 2.8.3 | 4 / 0 | |
| 2.8.2 | 4 / 0 | |
| 2.8.1 | 4 / 0 | |
| 2.8.0 | 4 / 0 | |
| 2.7.0 | 4 / 0 | |
| 2.6.3 | 4 / 0 | |
| 2.6.2 | 4 / 0 | |
| 2.6.1 | 4 / 0 | |
| 2.6.0 | 4 / 0 | |
| 2.5.2 | 4 / 0 | |
| 2.5.1 | 4 / 0 | |
| 2.5.0 | 4 / 0 | |
| 2.4.4 | 4 / 0 |
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.