@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@vaadin/breadcrumbs | AI (dependencies): First-party @vaadin scoped package added alongside other @vaadin deps in a minor version bump; consistent org pattern. | ai | |
| 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/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 | |
| phantom-deps | phantom-dep:@vaadin/field-base | AI (phantom-deps): Monorepo wrapper re-exports internal deps; stable pattern for this package. | ai |
Versions (showing 25 of 125)
| Version | Deps | Published |
|---|---|---|
| 24.5.5 | 59 / 0 | |
| 24.5.4 | 59 / 0 | |
| 24.5.3 | 59 / 0 | |
| 24.5.2 | 59 / 0 | |
| 24.5.1 | 59 / 0 | |
| 24.5.0 | 59 / 0 | |
| 24.4.18 | 58 / 0 | |
| 24.4.17 | 58 / 0 | |
| 24.4.16 | 58 / 0 | |
| 24.4.15 | 58 / 0 | |
| 24.4.14 | 58 / 0 | |
| 24.4.13 | 58 / 0 | |
| 24.4.12 | 58 / 0 | |
| 24.4.11 | 58 / 0 | |
| 24.4.10 | 58 / 0 | |
| 24.4.9 | 58 / 0 | |
| 24.4.8 | 58 / 0 | |
| 24.4.7 | 58 / 0 | |
| 24.4.6 | 58 / 0 | |
| 24.4.5 | 58 / 0 | |
| 24.4.4 | 58 / 0 | |
| 24.4.3 | 58 / 0 | |
| 24.4.2 | 58 / 0 | |
| 24.4.1 | 58 / 0 | |
| 24.4.0 | 58 / 0 |
v24.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.