@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 — 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 |
|---|---|---|---|---|
| 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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.7.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kylemcd) than the most recent previously approved version (cjbell) on 2026-06-05, but kylemcd is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.