@vaadin/lit-renderer
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:lit | AI (dependencies): lit is a well-known Google/Polymer-maintained library and is the expected core dependency for any Lit directive package; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Vaadin maintains multiple LTS branches; 24.9.x is a maintenance branch alongside the active 25.x series. Dormancy between LTS patch releases is expected behavior for this package. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin is an established vendor; lack of Sigstore provenance is common and not a risk signal for this well-known package family. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 1 / 4 | |
| 25.1.2 | 1 / 4 | |
| 25.1.1 | 1 / 4 | |
| 25.1.0 | 1 / 4 | |
| 25.0.12 | 1 / 4 | |
| 25.0.11 | 1 / 4 | |
| 25.0.10 | 1 / 4 | |
| 25.0.9 | 1 / 4 | |
| 25.0.8 | 1 / 4 | |
| 25.0.7 | 1 / 4 | |
| 25.0.6 | 1 / 4 | |
| 25.0.5 | 1 / 4 | |
| 25.0.4 | 1 / 4 | |
| 25.0.3 | 1 / 4 | |
| 25.0.2 | 1 / 4 | |
| 25.0.1 | 1 / 4 | |
| 25.0.0 | 1 / 4 | |
| 24.10.3 | 1 / 4 | |
| 24.10.2 | 1 / 4 | |
| 24.10.1 | 1 / 4 | |
| 24.10.0 | 1 / 4 | |
| 24.9.15 | 1 / 4 | |
| 24.9.14 | 1 / 4 | |
| 24.9.13 | 1 / 4 | |
| 24.9.12 | 1 / 4 | |
| 24.9.11 | 1 / 4 | |
| 24.9.10 | 1 / 4 | |
| 24.9.9 | 1 / 4 | |
| 24.9.8 | 1 / 4 | |
| 24.9.7 | 1 / 4 | |
| 24.9.6 | 1 / 4 | |
| 24.9.5 | 1 / 4 | |
| 24.9.4 | 1 / 4 | |
| 24.9.3 | 1 / 4 | |
| 24.8.14 | 1 / 4 | |
| 24.8.13 | 1 / 4 | |
| 24.8.12 | 1 / 4 | |
| 24.8.11 | 1 / 4 | |
| 24.8.10 | 1 / 4 | |
| 23.6.4 | 1 / 3 | |
| 23.6.3 | 1 / 3 |
v25.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.