@telegraph/button
Button component in Telegraph
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @telegraph/* packages; org does not use Sigstore attestation. | ai | |
| dependencies | unvetted-dep:@telegraph/icon | AI (dependencies): Same-org monorepo sibling; stable pattern across all @telegraph/* releases. | ai | |
| dependencies | unvetted-dep:@telegraph/layout | AI (dependencies): Same-org monorepo sibling; stable pattern across all @telegraph/* releases. | ai | |
| dependencies | unvetted-dep:@telegraph/typography | AI (dependencies): Same-org monorepo sibling; stable pattern across all @telegraph/* releases. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): lucide-react is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 0.7.4 | 7 / 11 | |
| 0.7.3 | 7 / 11 | |
| 0.7.2 | 7 / 11 | |
| 0.7.1 | 7 / 11 | |
| 0.7.0 | 7 / 11 | |
| 0.4.1 | 7 / 11 | |
| 0.4.0 | 7 / 11 | |
| 0.3.6 | 7 / 11 | |
| 0.3.5 | 7 / 11 | |
| 0.3.4 | 7 / 11 | |
| 0.3.3 | 7 / 11 | |
| 0.3.2 | 7 / 11 | |
| 0.3.1 | 7 / 11 | |
| 0.3.0 | 7 / 11 | |
| 0.2.7 | 7 / 11 | |
| 0.2.6 | 7 / 11 | |
| 0.2.5 | 7 / 11 | |
| 0.2.4 | 7 / 11 | |
| 0.2.3 | 7 / 11 | |
| 0.2.2 | 7 / 11 | |
| 0.2.1 | 7 / 11 | |
| 0.2.0 | 7 / 11 | |
| 0.1.4 | 7 / 11 | |
| 0.1.3 | 7 / 11 | |
| 0.1.2 | 7 / 11 | |
| 0.1.1 | 7 / 11 | |
| 0.1.0 | 7 / 11 | |
| 0.0.84 | 7 / 11 | |
| 0.0.83 | 7 / 11 | |
| 0.0.82 | 6 / 11 | |
| 0.0.81 | 6 / 11 | |
| 0.0.80 | 6 / 11 | |
| 0.0.79 | 6 / 11 | |
| 0.0.78 | 6 / 11 | |
| 0.0.77 | 6 / 11 | |
| 0.0.76 | 6 / 11 | |
| 0.0.75 | 6 / 11 | |
| 0.0.74 | 6 / 11 | |
| 0.0.73 | 6 / 11 | |
| 0.0.72 | 6 / 11 | |
| 0.0.71 | 6 / 11 | |
| 0.0.68 | 6 / 11 | |
| 0.0.67 | 6 / 11 | |
| 0.0.65 | 6 / 11 | |
| 0.0.64 | 6 / 11 | |
| 0.0.63 | 6 / 11 | |
| 0.0.62 | 6 / 11 | |
| 0.0.61 | 6 / 11 | |
| 0.0.60 | 6 / 11 | |
| 0.0.59 | 6 / 11 | |
| 0.0.58 | 6 / 11 | |
| 0.0.57 | 6 / 11 | |
| 0.0.56 | 7 / 12 | |
| 0.0.55 | 7 / 12 | |
| 0.0.54 | 7 / 12 | |
| 0.0.53 | 7 / 12 | |
| 0.0.52 | 7 / 12 | |
| 0.0.51 | 7 / 12 | |
| 0.0.50 | 7 / 12 | |
| 0.0.49 | 7 / 12 | |
| 0.0.48 | 7 / 12 | |
| 0.0.47 | 7 / 12 | |
| 0.0.46 | 7 / 12 | |
| 0.0.45 | 7 / 12 | |
| 0.0.44 | 7 / 12 | |
| 0.0.43 | 6 / 12 | |
| 0.0.42 | 6 / 12 | |
| 0.0.41 | 6 / 12 | |
| 0.0.40 | 6 / 12 | |
| 0.0.39 | 6 / 12 | |
| 0.0.38 | 6 / 12 | |
| 0.0.37 | 6 / 12 | |
| 0.0.36 | 6 / 12 | |
| 0.0.35 | 6 / 12 | |
| 0.0.34 | 6 / 12 | |
| 0.0.33 | 6 / 12 | |
| 0.0.32 | 4 / 14 | |
| 0.0.31 | 4 / 14 | |
| 0.0.30 | 4 / 14 | |
| 0.0.29 | 4 / 14 | |
| 0.0.28 | 4 / 14 | |
| 0.0.27 | 4 / 14 | |
| 0.0.26 | 4 / 14 | |
| 0.0.25 | 4 / 14 | |
| 0.0.24 | 4 / 14 | |
| 0.0.23 | 4 / 14 | |
| 0.0.22 | 4 / 14 | |
| 0.0.21 | 4 / 14 | |
| 0.0.20 | 4 / 14 | |
| 0.0.19 | 4 / 14 | |
| 0.0.18 | 4 / 14 | |
| 0.0.17 | 4 / 14 | |
| 0.0.16 | 4 / 14 | |
| 0.0.15 | 4 / 14 | |
| 0.0.14 | 4 / 14 |
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.