← Home

@radix-ui/react-tabs

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/components/tabs).

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): chancestrickland is a known Radix/WorkOS maintainer; legitimate org transition. ai
maintainer-change maintainer-added AI (maintainer-change): WorkOS acquisition of Radix UI; new maintainers are known team members. ai
maintainer-change maintainer-removed AI (maintainer-change): Old maintainers removed as part of WorkOS org transition. ai
publish-pattern dormant-publish AI (publish-pattern): Version gap reflects monorepo restructuring, not suspicious dormancy. ai
bogus-package bogus-package AI (bogus-package): Radix UI primitives are well-known; sparse README is a monorepo artifact. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.15 8 / 7
1.1.14 8 / 7
1.1.13 8 / 9
1.0.2 9 / 0

v1.1.15

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.14

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-06-06. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.13

2 findings
HIGH Publisher changed: benoitgrelard → chancestrickland (on 2025-08-13) provenance

This version was published by a different npm account than previous versions on 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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