@telegraph/input
Input component for 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 | publisher-changed | AI (provenance): cjbell is an established knocklabs publisher (191 approved); transition appears legitimate within the same org. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @telegraph/* packages; monorepo does not use Sigstore attestation. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 5 / 11 | |
| 0.4.1 | 6 / 11 | |
| 0.4.0 | 6 / 11 | |
| 0.3.2 | 6 / 11 | |
| 0.3.1 | 6 / 11 | |
| 0.3.0 | 6 / 11 | |
| 0.2.2 | 6 / 11 | |
| 0.2.1 | 6 / 11 | |
| 0.2.0 | 6 / 11 | |
| 0.1.7 | 6 / 11 | |
| 0.1.6 | 6 / 11 | |
| 0.1.5 | 6 / 11 | |
| 0.1.4 | 6 / 11 | |
| 0.1.3 | 6 / 11 | |
| 0.1.2 | 6 / 11 | |
| 0.1.1 | 6 / 11 | |
| 0.1.0 | 6 / 11 | |
| 0.0.49 | 6 / 11 | |
| 0.0.48 | 6 / 11 | |
| 0.0.47 | 6 / 12 | |
| 0.0.46 | 6 / 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.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 | 5 / 12 | |
| 0.0.23 | 5 / 12 | |
| 0.0.22 | 5 / 12 | |
| 0.0.21 | 5 / 12 | |
| 0.0.20 | 5 / 12 | |
| 0.0.19 | 5 / 12 | |
| 0.0.18 | 5 / 12 | |
| 0.0.17 | 5 / 12 | |
| 0.0.16 | 5 / 12 | |
| 0.0.15 | 5 / 12 | |
| 0.0.14 | 5 / 14 |
v0.4.2
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.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.