@vaadin/tabs No license 36 versions

@vaadin/tabs

npm Repository Homepage

36

Versions

—

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

Keywords

Vaadinvaadin-tabsweb-componentsweb-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Vaadin regularly backports to older release branches; dormancy between minor series is expected.	ai	2026/05/15
publish-pattern	new-deps-added	AI (publish-pattern): @polymer/polymer and vaadin theme packages are standard 24.x series deps; not suspicious for this vendor.	ai	2026/05/15
source-diff	large-new-source-files	AI (source-diff): Older 24.x branch has different file layout vs 25.x; extra files reflect branch differences, not injected code.	ai	2026/05/15
dependencies	unvetted-dep:@vaadin/item	AI (dependencies): Sibling Vaadin monorepo component; same versioning scheme, not a third-party risk.	ai	2026/04/30

Versions (showing 36 of 36)

Version	Deps	Published
25.1.3	6 / 6	2026-05-11
25.1.2	6 / 6	2026-04-24
25.1.1	6 / 6	2026-04-16
25.1.0	6 / 6	2026-03-24
25.0.12	6 / 6	2026-05-11
25.0.11	6 / 6	2026-04-24
25.0.10	6 / 6	2026-04-20
25.0.9	6 / 6	2026-03-26
25.0.8	6 / 6	2026-03-13
25.0.7	6 / 6	2026-03-06
25.0.5	6 / 6	2026-02-27
25.0.4	6 / 6	2026-02-06
25.0.3	6 / 6	2026-01-16
25.0.2	6 / 5	2026-01-09
25.0.1	6 / 5	2025-12-22
25.0.0	6 / 5	2025-12-16
24.10.3	9 / 4	2026-05-21
24.10.2	9 / 4	2026-05-20
24.10.1	9 / 4	2026-04-24
24.10.0	9 / 4	2026-03-17
24.9.15	9 / 4	2026-05-21
24.9.14	9 / 4	2026-04-24
24.9.13	9 / 4	2026-03-13
24.9.12	9 / 4	2026-03-06
24.9.11	9 / 4	2026-02-27
24.9.10	9 / 4	2026-01-16
24.9.9	9 / 4	2026-01-12
24.9.8	9 / 4	2026-01-09
24.9.7	9 / 4	2025-12-22
24.9.6	9 / 4	2025-11-26
24.9.5	9 / 4	2025-11-07
24.8.14	9 / 4	2025-12-16
24.8.13	9 / 4	2025-11-26
24.8.12	9 / 4	2025-11-07
23.6.4	7 / 3	2026-03-11
23.6.3	7 / 3	2026-02-17

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

v24.10.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.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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

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.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.

v23.6.4

1 finding

LOW No provenance attestation provenance

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

v23.6.3

1 finding

LOW No provenance attestation provenance

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