@telegraph/tooltip
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 for this package. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 6 / 11 | |
| 0.4.1 | 7 / 11 | |
| 0.4.0 | 7 / 11 | |
| 0.3.0 | 7 / 11 | |
| 0.1.3 | 7 / 11 | |
| 0.1.2 | 7 / 11 | |
| 0.1.1 | 7 / 11 | |
| 0.1.0 | 7 / 11 | |
| 0.0.62 | 7 / 11 | |
| 0.0.61 | 7 / 11 | |
| 0.0.60 | 7 / 11 | |
| 0.0.59 | 7 / 11 | |
| 0.0.58 | 7 / 11 | |
| 0.0.57 | 7 / 11 | |
| 0.0.56 | 7 / 11 | |
| 0.0.55 | 7 / 11 | |
| 0.0.54 | 7 / 11 | |
| 0.0.53 | 7 / 11 | |
| 0.0.52 | 7 / 11 | |
| 0.0.51 | 7 / 11 | |
| 0.0.50 | 7 / 11 | |
| 0.0.49 | 7 / 11 | |
| 0.0.48 | 7 / 11 | |
| 0.0.47 | 7 / 11 | |
| 0.0.46 | 7 / 11 | |
| 0.0.45 | 7 / 11 | |
| 0.0.44 | 7 / 11 | |
| 0.0.43 | 7 / 11 | |
| 0.0.42 | 7 / 11 | |
| 0.0.41 | 7 / 11 | |
| 0.0.40 | 7 / 11 | |
| 0.0.39 | 7 / 11 | |
| 0.0.36 | 7 / 11 | |
| 0.0.35 | 7 / 11 | |
| 0.0.34 | 7 / 11 | |
| 0.0.33 | 7 / 11 | |
| 0.0.32 | 7 / 11 | |
| 0.0.31 | 7 / 11 | |
| 0.0.30 | 7 / 11 | |
| 0.0.29 | 7 / 12 | |
| 0.0.28 | 7 / 12 | |
| 0.0.27 | 7 / 12 | |
| 0.0.26 | 7 / 12 | |
| 0.0.25 | 7 / 12 | |
| 0.0.24 | 7 / 12 | |
| 0.0.23 | 7 / 12 | |
| 0.0.22 | 7 / 12 | |
| 0.0.21 | 7 / 12 | |
| 0.0.20 | 6 / 12 | |
| 0.0.19 | 6 / 12 | |
| 0.0.18 | 6 / 12 | |
| 0.0.17 | 6 / 12 | |
| 0.0.16 | 6 / 12 | |
| 0.0.15 | 6 / 12 | |
| 0.0.14 | 6 / 12 | |
| 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 | |
| 0.0.4 | 7 / 14 | |
| 0.0.3 | 7 / 14 | |
| 0.0.2 | 7 / 14 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
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.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
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. Only ~12% of npm packages have provenance, so this is common but not ideal.