@telegraph/tabs
Standardized tabs component for navigation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@telegraph/icon | AI (phantom-deps): Same-org monorepo dep; may be re-exported or used indirectly via peer components. | ai | |
| phantom-deps | phantom-dep:@telegraph/button | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@telegraph/typography | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 7 / 11 | |
| 0.1.7 | 7 / 11 | |
| 0.1.6 | 7 / 11 | |
| 0.1.4 | 7 / 11 | |
| 0.1.0 | 7 / 11 | |
| 0.0.34 | 7 / 11 | |
| 0.0.33 | 7 / 11 | |
| 0.0.32 | 7 / 11 | |
| 0.0.31 | 7 / 11 | |
| 0.0.30 | 7 / 11 | |
| 0.0.29 | 7 / 11 | |
| 0.0.28 | 7 / 11 | |
| 0.0.27 | 7 / 11 | |
| 0.0.26 | 7 / 11 | |
| 0.0.25 | 7 / 11 | |
| 0.0.24 | 7 / 11 | |
| 0.0.23 | 7 / 11 | |
| 0.0.22 | 7 / 11 | |
| 0.0.21 | 7 / 11 | |
| 0.0.20 | 7 / 11 | |
| 0.0.19 | 7 / 11 | |
| 0.0.18 | 7 / 11 | |
| 0.0.17 | 7 / 11 | |
| 0.0.16 | 7 / 11 | |
| 0.0.15 | 7 / 11 | |
| 0.0.14 | 7 / 11 | |
| 0.0.13 | 7 / 11 | |
| 0.0.12 | 7 / 11 | |
| 0.0.11 | 7 / 11 | |
| 0.0.10 | 7 / 11 | |
| 0.0.9 | 7 / 11 | |
| 0.0.8 | 7 / 11 | |
| 0.0.7 | 7 / 11 | |
| 0.0.6 | 7 / 11 | |
| 0.0.5 | 7 / 11 | |
| 0.0.4 | 7 / 11 | |
| 0.0.3 | 7 / 11 | |
| 0.0.2 | 7 / 11 | |
| 0.0.1 | 7 / 11 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.