@vaadin/sso-kit-client-lit
SSO Kit Client Lit
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:@vaadin/router | AI (dependencies): First-party Vaadin dependency; stable and well-known in the Vaadin ecosystem. | ai | |
| dependencies | unvetted-dep:@vaadin/hilla-frontend | AI (dependencies): First-party Vaadin/Hilla dependency; expected transitive dep for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; declared in dependencies, used by transpiled output. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 3 / 20 | |
| 4.1.1 | 3 / 20 | |
| 4.1.0 | 3 / 20 | |
| 4.0.2 | 3 / 20 | |
| 4.0.1 | 3 / 20 | |
| 4.0.0 | 3 / 20 | |
| 3.2.4 | 3 / 20 | |
| 3.2.3 | 3 / 20 | |
| 3.2.2 | 3 / 20 |
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.