@lmvz-ds/angular UNLICENSED 31 versions

@lmvz-ds/angular

npm Repository

This is the Angular wrapper library generated from the LMVZ-DS Components package via [Stencil](https://stenciljs.com/).

31

Versions

UNLICENSED

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nmzpadsat

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Likely a CI/CD environment change; no other risk signals present and package content is consistent with prior versions.	ai	2026/05/27
bogus-package	bogus-package	AI (bogus-package): Internal/private design-system package; sparse README and no keywords are expected for this type of package.	ai	2026/05/13
phantom-deps	phantom-dep:@angular/compiler	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05
phantom-deps	phantom-dep:@angular/animations	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05
phantom-deps	phantom-dep:@angular/platform-browser	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05
phantom-deps	phantom-dep:@angular/common	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05
phantom-deps	phantom-dep:zone.js	AI (phantom-deps): Zone.js is Angular runtime dependency, loaded by convention.	ai	2026/05/05
phantom-deps	phantom-dep:@lmvz-ds/styles	AI (phantom-deps): Same-org scoped package, loaded by convention in monorepo.	ai	2026/05/05
phantom-deps	phantom-dep:@angular/platform-browser-dynamic	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05
phantom-deps	phantom-dep:@angular/router	AI (phantom-deps): Angular framework packages loaded by convention in component libraries.	ai	2026/05/05

Versions (showing 31 of 31)

Version	Deps	Published
0.25.0	1 / 0	2026-06-03
0.24.0	1 / 0	2026-06-01
0.23.0	1 / 0	2026-05-28
0.22.1	1 / 0	2026-05-26
0.22.0	1 / 0	2026-05-22
0.21.0	1 / 0	2026-05-21
0.20.0	1 / 0	2026-05-20
0.19.0	1 / 0	2026-05-18
0.18.2	1 / 0	2026-05-18
0.18.1	1 / 0	2026-05-13
0.18.0	1 / 0	2026-04-30
0.17.3	1 / 0	2026-04-23
0.17.1	13 / 7	2026-04-08
0.17.0	13 / 7	2026-04-08
0.16.0	13 / 7	2026-03-30
0.15.2	1 / 0	2026-03-23
0.15.1	1 / 0	2026-03-23
0.15.0	1 / 0	2026-03-23
0.14.1	1 / 0	2026-03-23
0.14.0	1 / 0	2026-03-20
0.13.3	1 / 0	2026-03-17
0.13.2	1 / 0	2026-03-17
0.13.1	1 / 0	2026-03-13
0.13.0	1 / 0	2026-03-13
0.12.5	1 / 0	2026-03-11
0.12.4	1 / 0	2026-03-10
0.12.3	1 / 0	2026-03-10
0.12.2	1 / 0	2026-03-09
0.12.1	1 / 0	2026-03-09
0.12.0	1 / 0	2026-03-09
0.11.4	1 / 0	2026-03-09

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.22.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.21.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.20.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.19.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.18.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.18.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nmzpadsat.

LOW No provenance attestation provenance

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

v0.18.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.

v0.17.3

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.

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

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.5

1 finding

LOW No provenance attestation provenance

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

v0.12.4

1 finding

LOW No provenance attestation provenance

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

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.2

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.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.

v0.11.4

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.