@vaadin/react-components-pro SEE LICENSE IN LICENSE 51 versions

@vaadin/react-components-pro

npm Repository

React wrappers for commercial Vaadin components

51

Versions

SEE LICENSE IN LICENSE

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

web-padawandiegocardosoalvarezguilleplatoshajounimanoloyuriyyevvaadin-ownertomivirkkiartur-sunzhewyqsissbruecker

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	2026/05/24
provenance	no-provenance	AI (provenance): Vaadin org consistently publishes without Sigstore provenance; stable false positive for this package.	ai	2026/05/23
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	2026/05/08
dependencies	unvetted-dep:@vaadin/cookie-consent	AI (dependencies): First-party Vaadin package; consistent with all other @vaadin/* deps in this bundle.	ai	2026/05/08
bogus-package	bogus-package	AI (bogus-package): Commercial Vaadin component library; sparse README and no keywords are expected for this package type.	ai	2026/05/04

Versions (showing 51 of 60)

View all versions

Version	Deps	Published
25.1.3	9 / 0	2026-05-11
25.1.2	9 / 0	2026-04-24
25.1.1	9 / 0	2026-04-16
25.1.0	9 / 0	2026-03-24
25.0.12	9 / 0	2026-05-11
25.0.11	9 / 0	2026-04-24
25.0.10	9 / 0	2026-04-20
25.0.9	9 / 0	2026-03-26
25.0.8	9 / 0	2026-03-13
25.0.7	9 / 0	2026-03-06
25.0.5	9 / 0	2026-02-27
25.0.4	9 / 0	2026-02-06
25.0.3	9 / 0	2026-01-16
25.0.2	9 / 0	2026-01-09
25.0.1	9 / 0	2025-12-22
25.0.0	9 / 0	2025-12-16
24.10.3	10 / 0	2026-05-21
24.10.2	10 / 0	2026-05-20
24.10.1	10 / 0	2026-04-24
24.10.0	10 / 0	2026-03-17
24.9.15	10 / 0	2026-05-21
24.9.14	10 / 0	2026-04-24
24.9.13	10 / 0	2026-03-13
24.9.12	10 / 0	2026-03-06
24.9.11	10 / 0	2026-02-27
24.9.10	10 / 0	2026-01-16
24.9.9	10 / 0	2026-01-12
24.9.8	10 / 0	2026-01-09
24.9.7	10 / 0	2025-12-22
24.9.6	10 / 0	2025-11-26
24.9.5	10 / 0	2025-11-07
24.9.4	10 / 0	2025-10-28
24.9.3	10 / 0	2025-10-28
24.9.2	10 / 0	2025-10-03
24.9.1	10 / 0	2025-09-24
24.9.0	10 / 0	2025-09-15
24.8.14	10 / 0	2025-12-16
24.8.13	10 / 0	2025-11-26
24.8.12	10 / 0	2025-11-07
24.8.11	10 / 0	2025-10-29
24.8.10	10 / 0	2025-10-28
24.8.9	10 / 0	2025-10-03
24.8.8	10 / 0	2025-09-24
24.8.7	10 / 0	2025-09-05
24.8.6	10 / 0	2025-08-25
24.8.5	10 / 0	2025-08-08
24.8.4	10 / 0	2025-07-18
24.8.3	10 / 0	2025-07-07
24.8.2	10 / 0	2025-07-01
24.8.1	10 / 0	2025-06-27
24.8.0	10 / 0	2025-06-16

v25.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.2

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.1

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.9.0

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.8.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.8.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.9

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.8

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.7

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.6

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.5

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.4

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.3

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.2

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.1

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.8.0

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.