@atlaskit/tabs
Tabs are used to organize content by grouping similar information on the same page.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlaskit dependency from the same org scope; standard internal dep for Atlaskit UI components. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party Atlaskit dependency from the same org scope; standard internal dep for Atlaskit UI components. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party Atlaskit dependency from the same org scope; standard internal dep for Atlaskit UI components. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlaskit dependency from the same org scope; standard internal dep for Atlaskit UI components. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org Atlaskit package; phantom dep pattern is expected in Atlaskit monorepo entry-point sub-packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org Atlaskit package; phantom dep pattern is expected in Atlaskit monorepo entry-point sub-packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 19.1.0 | 6 / 21 | |
| 19.0.5 | 6 / 21 | |
| 19.0.4 | 6 / 21 | |
| 19.0.3 | 6 / 21 | |
| 19.0.2 | 6 / 20 | |
| 19.0.1 | 6 / 20 | |
| 19.0.0 | 7 / 20 | |
| 18.3.5 | 7 / 19 | |
| 18.3.4 | 7 / 19 | |
| 18.3.3 | 7 / 19 | |
| 18.3.2 | 7 / 19 | |
| 18.3.1 | 7 / 18 | |
| 18.3.0 | 7 / 18 | |
| 18.2.5 | 6 / 18 | |
| 18.2.4 | 7 / 19 |
v19.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.