@vaadin/react-components
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:jouni.me | AI (email-domain): Vaadin-owner publisher has 544 approved packages; individual maintainer email domain lapse is low-risk in this context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate wrapper library; sparse README/keywords are typical for component library sub-packages. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-material-styles | AI (phantom-deps): Monorepo wrapper re-exports internal Vaadin deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/field-base | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/lit-renderer | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/component-base | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/icons | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/field-highlighter | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-lumo-styles | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/input-container | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/overlay | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/a11y-base | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 63 / 0 | |
| 25.1.2 | 63 / 0 | |
| 25.1.1 | 63 / 0 | |
| 25.1.0 | 63 / 0 | |
| 25.0.12 | 61 / 0 | |
| 25.0.11 | 61 / 0 | |
| 25.0.10 | 61 / 0 | |
| 25.0.9 | 61 / 0 | |
| 25.0.8 | 61 / 0 | |
| 25.0.7 | 61 / 0 | |
| 25.0.5 | 61 / 0 | |
| 25.0.4 | 61 / 0 | |
| 25.0.3 | 61 / 0 | |
| 25.0.2 | 61 / 0 | |
| 25.0.1 | 61 / 0 | |
| 25.0.0 | 61 / 0 | |
| 24.10.3 | 62 / 0 | |
| 24.10.2 | 62 / 0 | |
| 24.10.1 | 62 / 0 | |
| 24.10.0 | 62 / 0 | |
| 24.9.15 | 62 / 0 | |
| 24.9.14 | 62 / 0 | |
| 24.9.13 | 62 / 0 | |
| 24.9.12 | 62 / 0 | |
| 24.9.11 | 62 / 0 | |
| 24.9.10 | 62 / 0 | |
| 24.9.9 | 62 / 0 | |
| 24.9.8 | 62 / 0 | |
| 24.9.7 | 62 / 0 | |
| 24.9.6 | 62 / 0 | |
| 24.9.5 | 62 / 0 | |
| 24.9.4 | 62 / 0 | |
| 24.9.3 | 62 / 0 | |
| 24.9.2 | 62 / 0 | |
| 24.9.1 | 62 / 0 | |
| 24.9.0 | 62 / 0 | |
| 24.8.14 | 62 / 0 | |
| 24.8.13 | 62 / 0 | |
| 24.8.12 | 62 / 0 | |
| 24.8.11 | 62 / 0 | |
| 24.8.10 | 62 / 0 | |
| 24.8.9 | 62 / 0 | |
| 24.8.8 | 62 / 0 | |
| 24.8.7 | 62 / 0 | |
| 24.8.6 | 62 / 0 | |
| 24.8.5 | 62 / 0 | |
| 24.8.4 | 62 / 0 | |
| 24.8.3 | 62 / 0 | |
| 24.8.2 | 62 / 0 | |
| 24.8.1 | 62 / 0 | |
| 24.8.0 | 62 / 0 |
v25.1.3
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.2
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.1
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.0
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.9
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.8
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.7
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.6
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.5
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.4
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.3
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.2
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.1
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.0
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.