@telegraph/segmented-control
A segmented selection between as set of options.
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:motion | AI (phantom-deps): motion is a declared runtime dependency; phantom-dep is a false positive here. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 8 / 11 | |
| 0.3.1 | 8 / 11 | |
| 0.3.0 | 8 / 11 | |
| 0.2.7 | 7 / 11 | |
| 0.2.6 | 7 / 11 | |
| 0.2.5 | 7 / 11 | |
| 0.2.1 | 7 / 11 | |
| 0.2.0 | 7 / 11 | |
| 0.1.20 | 7 / 11 | |
| 0.1.19 | 7 / 11 | |
| 0.1.18 | 7 / 11 | |
| 0.1.17 | 7 / 11 | |
| 0.1.16 | 7 / 11 | |
| 0.1.15 | 4 / 11 | |
| 0.1.14 | 4 / 11 | |
| 0.1.13 | 4 / 11 | |
| 0.1.12 | 4 / 11 | |
| 0.1.11 | 4 / 11 | |
| 0.1.10 | 4 / 11 | |
| 0.1.9 | 4 / 11 | |
| 0.1.8 | 4 / 11 | |
| 0.1.7 | 4 / 11 | |
| 0.1.6 | 4 / 11 | |
| 0.1.5 | 4 / 11 | |
| 0.1.4 | 4 / 11 | |
| 0.1.3 | 4 / 11 | |
| 0.1.2 | 4 / 11 | |
| 0.1.1 | 4 / 11 | |
| 0.1.0 | 4 / 11 | |
| 0.0.44 | 4 / 11 | |
| 0.0.43 | 4 / 11 | |
| 0.0.42 | 4 / 11 | |
| 0.0.41 | 4 / 11 | |
| 0.0.40 | 4 / 11 | |
| 0.0.39 | 4 / 11 | |
| 0.0.38 | 4 / 11 | |
| 0.0.37 | 4 / 11 | |
| 0.0.36 | 4 / 11 | |
| 0.0.35 | 4 / 11 | |
| 0.0.34 | 4 / 11 | |
| 0.0.33 | 4 / 11 | |
| 0.0.32 | 4 / 11 | |
| 0.0.31 | 4 / 11 | |
| 0.0.28 | 4 / 11 | |
| 0.0.27 | 4 / 11 | |
| 0.0.25 | 4 / 11 | |
| 0.0.24 | 4 / 11 | |
| 0.0.23 | 4 / 11 | |
| 0.0.22 | 4 / 11 | |
| 0.0.21 | 4 / 11 | |
| 0.0.20 | 4 / 11 | |
| 0.0.19 | 4 / 11 | |
| 0.0.18 | 4 / 11 | |
| 0.0.17 | 4 / 11 | |
| 0.0.16 | 4 / 11 | |
| 0.0.15 | 4 / 11 | |
| 0.0.14 | 4 / 11 | |
| 0.0.13 | 4 / 11 | |
| 0.0.12 | 4 / 11 | |
| 0.0.11 | 4 / 11 | |
| 0.0.10 | 4 / 11 | |
| 0.0.9 | 4 / 11 | |
| 0.0.8 | 4 / 11 | |
| 0.0.7 | 4 / 11 | |
| 0.0.6 | 4 / 11 | |
| 0.0.5 | 4 / 11 | |
| 0.0.4 | 4 / 11 | |
| 0.0.3 | 4 / 11 | |
| 0.0.2 | 4 / 11 | |
| 0.0.1 | 4 / 11 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.