@dxos/react-ui-tabs
Components for facilitating a Tabs pattern.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): DXOS monorepo migrated publishing from dxos-bot to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal aligns with org-level CI pipeline transition; no malicious indicators present. | ai | |
| phantom-deps | phantom-dep:@dxos/util | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/primitive | AI (phantom-deps): Radix UI dep referenced in config; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Radix UI dep referenced in config; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-primitive | AI (phantom-deps): Radix UI dep referenced in config; stable false positive for this UI component package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 9 / 9 | |
| 0.9.0 | 9 / 9 | |
| 0.8.3 | 10 / 9 | |
| 0.8.2 | 10 / 9 | |
| 0.8.1 | 9 / 9 | |
| 0.8.0 | 9 / 9 | |
| 0.7.4 | 8 / 9 | |
| 0.7.3 | 8 / 9 | |
| 0.7.2 | 8 / 9 | |
| 0.7.1 | 8 / 9 | |
| 0.7.0 | 8 / 9 | |
| 0.6.13 | 10 / 7 | |
| 0.6.12 | 10 / 7 | |
| 0.6.11 | 10 / 7 | |
| 0.6.10 | 10 / 7 | |
| 0.6.9 | 10 / 7 | |
| 0.6.8 | 10 / 7 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.