@telegraph/radio
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 | publisher-changed | AI (provenance): cjbell is an established publisher (190 approved) within the @knocklabs org; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Entire @telegraph/* monorepo publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@telegraph/button | AI (dependencies): Sibling package in the same knocklabs/telegraph monorepo; expected internal dependency. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Radio button UI component in knocklabs/telegraph monorepo; name similarity to redis is coincidental. | ai | |
| dependencies | unvetted-dep:@telegraph/helpers | AI (dependencies): Sibling package in the same knocklabs/telegraph monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@telegraph/layout | AI (dependencies): Sibling package in the same knocklabs/telegraph monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@telegraph/icon | AI (dependencies): Sibling package in the same knocklabs/telegraph monorepo; expected internal dependency. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 5 / 11 | |
| 0.1.3 | 5 / 11 | |
| 0.1.2 | 5 / 11 | |
| 0.1.1 | 5 / 11 | |
| 0.1.0 | 5 / 11 | |
| 0.0.92 | 5 / 11 | |
| 0.0.91 | 5 / 11 | |
| 0.0.90 | 5 / 11 | |
| 0.0.89 | 5 / 11 | |
| 0.0.88 | 5 / 11 | |
| 0.0.87 | 5 / 11 | |
| 0.0.86 | 5 / 11 | |
| 0.0.85 | 5 / 11 | |
| 0.0.84 | 5 / 11 | |
| 0.0.83 | 5 / 11 | |
| 0.0.82 | 5 / 11 | |
| 0.0.81 | 5 / 11 | |
| 0.0.80 | 5 / 11 | |
| 0.0.79 | 5 / 11 | |
| 0.0.78 | 5 / 11 | |
| 0.0.77 | 5 / 11 | |
| 0.0.76 | 5 / 11 | |
| 0.0.75 | 5 / 11 | |
| 0.0.74 | 5 / 11 | |
| 0.0.73 | 5 / 11 | |
| 0.0.72 | 5 / 11 | |
| 0.0.71 | 5 / 11 | |
| 0.0.70 | 5 / 12 | |
| 0.0.69 | 5 / 12 | |
| 0.0.68 | 5 / 12 | |
| 0.0.67 | 5 / 12 | |
| 0.0.66 | 5 / 12 | |
| 0.0.65 | 5 / 12 | |
| 0.0.64 | 5 / 12 | |
| 0.0.63 | 5 / 12 | |
| 0.0.62 | 5 / 12 | |
| 0.0.61 | 5 / 12 | |
| 0.0.60 | 5 / 12 | |
| 0.0.59 | 5 / 12 | |
| 0.0.58 | 5 / 12 | |
| 0.0.55 | 5 / 12 | |
| 0.0.54 | 5 / 12 | |
| 0.0.52 | 5 / 12 | |
| 0.0.51 | 5 / 12 | |
| 0.0.50 | 5 / 12 | |
| 0.0.49 | 5 / 12 | |
| 0.0.48 | 5 / 12 | |
| 0.0.47 | 5 / 12 | |
| 0.0.46 | 5 / 12 | |
| 0.0.45 | 6 / 12 | |
| 0.0.44 | 6 / 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 | 6 / 12 | |
| 0.0.31 | 6 / 12 | |
| 0.0.30 | 6 / 12 | |
| 0.0.29 | 6 / 12 | |
| 0.0.28 | 6 / 12 | |
| 0.0.27 | 6 / 12 | |
| 0.0.26 | 6 / 12 | |
| 0.0.25 | 6 / 12 | |
| 0.0.24 | 6 / 12 | |
| 0.0.23 | 6 / 12 | |
| 0.0.22 | 6 / 12 | |
| 0.0.21 | 6 / 12 | |
| 0.0.20 | 6 / 12 | |
| 0.0.19 | 6 / 12 | |
| 0.0.18 | 6 / 12 | |
| 0.0.17 | 7 / 14 | |
| 0.0.16 | 7 / 14 | |
| 0.0.15 | 7 / 14 | |
| 0.0.14 | 7 / 14 | |
| 0.0.13 | 7 / 14 | |
| 0.0.12 | 7 / 14 | |
| 0.0.11 | 7 / 14 | |
| 0.0.10 | 7 / 14 | |
| 0.0.9 | 7 / 14 | |
| 0.0.8 | 7 / 14 | |
| 0.0.7 | 7 / 14 | |
| 0.0.6 | 7 / 14 | |
| 0.0.5 | 7 / 14 |
v0.1.4
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-09, 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.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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.