@vaadin/react-components-pro
React wrappers for commercial Vaadin 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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:jouni.me | AI (email-domain): Vaadin is an established commercial vendor; single maintainer email domain risk is low given the publisher's long track record. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin org consistently publishes without Sigstore provenance; stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @vaadin/* component at matching pinned version; consistent with package's pattern of wrapping Vaadin pro components. | ai | |
| dependencies | unvetted-dep:@vaadin/cookie-consent | AI (dependencies): First-party Vaadin package; consistent with all other @vaadin/* deps in this bundle. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Commercial Vaadin component library; sparse README and no keywords are expected for this package type. | ai |
Versions (showing 25 of 125)
| Version | Deps | Published |
|---|---|---|
| 24.5.5 | 9 / 0 | |
| 24.5.4 | 9 / 0 | |
| 24.5.3 | 9 / 0 | |
| 24.5.2 | 9 / 0 | |
| 24.5.1 | 9 / 0 | |
| 24.5.0 | 9 / 0 | |
| 24.4.18 | 9 / 0 | |
| 24.4.17 | 9 / 0 | |
| 24.4.16 | 9 / 0 | |
| 24.4.15 | 9 / 0 | |
| 24.4.14 | 9 / 0 | |
| 24.4.13 | 9 / 0 | |
| 24.4.12 | 9 / 0 | |
| 24.4.11 | 9 / 0 | |
| 24.4.10 | 9 / 0 | |
| 24.4.9 | 9 / 0 | |
| 24.4.8 | 9 / 0 | |
| 24.4.7 | 9 / 0 | |
| 24.4.6 | 9 / 0 | |
| 24.4.5 | 9 / 0 | |
| 24.4.4 | 9 / 0 | |
| 24.4.3 | 9 / 0 | |
| 24.4.2 | 9 / 0 | |
| 24.4.1 | 9 / 0 | |
| 24.4.0 | 9 / 0 |
v24.5.5
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.5.4
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.5.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.5.2
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.5.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.
v24.5.0
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.4.18
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.4.17
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.4.16
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.4.15
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.4.14
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.4.13
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.4.12
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.4.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.4.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.
v24.4.9
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.4.8
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.4.7
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.4.6
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.4.5
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.4.4
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.4.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.4.2
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.4.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.
v24.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.