@times-components/link
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @times-components/link is a legitimate Times UK component; Levenshtein match to 'pino' is a false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared peer/dev dep used in test config; stable false positive for this package. | ai |
Versions (showing 100 of 145)
| Version | Deps | Published |
|---|---|---|
| 3.18.47 | 6 / 17 | |
| 3.18.46 | 6 / 17 | |
| 3.18.45 | 6 / 17 | |
| 3.18.44 | 6 / 17 | |
| 3.18.43 | 6 / 17 | |
| 3.18.42 | 6 / 17 | |
| 3.18.41 | 6 / 17 | |
| 3.18.40 | 6 / 17 | |
| 3.18.39 | 6 / 17 | |
| 3.18.38 | 6 / 17 | |
| 3.18.37 | 6 / 17 | |
| 3.18.36 | 6 / 17 | |
| 3.18.35 | 6 / 17 | |
| 3.18.34 | 6 / 17 | |
| 3.18.33 | 6 / 17 | |
| 3.18.32 | 6 / 17 | |
| 3.18.31 | 6 / 17 | |
| 3.18.30 | 6 / 17 | |
| 3.18.29 | 6 / 17 | |
| 3.18.28 | 6 / 17 | |
| 3.18.27 | 6 / 17 | |
| 3.18.26 | 6 / 17 | |
| 3.18.25 | 6 / 17 | |
| 3.18.24 | 6 / 17 | |
| 3.18.23 | 6 / 17 | |
| 3.18.22 | 6 / 17 | |
| 3.18.21 | 6 / 17 | |
| 3.18.20 | 6 / 17 | |
| 3.18.19 | 6 / 17 | |
| 3.18.18 | 6 / 17 | |
| 3.18.17 | 6 / 17 | |
| 3.18.16 | 6 / 17 | |
| 3.18.15 | 6 / 17 | |
| 3.18.14 | 6 / 17 | |
| 3.18.13 | 6 / 17 | |
| 3.18.12 | 6 / 17 | |
| 3.18.11 | 6 / 17 | |
| 3.18.10 | 6 / 17 | |
| 3.18.9 | 6 / 17 | |
| 3.18.8 | 6 / 17 | |
| 3.18.7 | 6 / 17 | |
| 3.18.6 | 6 / 17 | |
| 3.18.5 | 6 / 17 | |
| 3.18.4 | 6 / 17 | |
| 3.18.3 | 6 / 17 | |
| 3.18.2 | 6 / 17 | |
| 3.18.1 | 6 / 17 | |
| 3.18.0 | 6 / 17 | |
| 3.17.47 | 6 / 17 | |
| 3.17.46 | 6 / 17 | |
| 3.17.45 | 6 / 17 | |
| 3.17.44 | 6 / 17 | |
| 3.17.43 | 6 / 17 | |
| 3.17.42 | 6 / 17 | |
| 3.17.41 | 6 / 17 | |
| 3.17.40 | 6 / 17 | |
| 3.17.39 | 6 / 17 | |
| 3.17.38 | 6 / 17 | |
| 3.17.37 | 6 / 17 | |
| 3.17.36 | 6 / 17 | |
| 3.17.35 | 6 / 17 | |
| 3.17.34 | 6 / 17 | |
| 3.17.33 | 6 / 17 | |
| 3.17.32 | 6 / 17 | |
| 3.17.31 | 6 / 17 | |
| 3.17.30 | 6 / 17 | |
| 3.17.29 | 6 / 17 | |
| 3.17.28 | 6 / 17 | |
| 3.17.27 | 6 / 17 | |
| 3.17.26 | 6 / 17 | |
| 3.17.25 | 6 / 17 | |
| 3.17.24 | 6 / 17 | |
| 3.17.23 | 6 / 17 | |
| 3.17.22 | 6 / 17 | |
| 3.17.21 | 6 / 17 | |
| 3.17.20 | 6 / 17 | |
| 3.17.19 | 6 / 17 | |
| 3.17.18 | 6 / 17 | |
| 3.17.17 | 6 / 17 | |
| 3.17.16 | 6 / 17 | |
| 3.17.15 | 6 / 17 | |
| 3.17.14 | 6 / 17 | |
| 3.17.13 | 6 / 17 | |
| 3.17.12 | 6 / 17 | |
| 3.17.11 | 6 / 17 | |
| 3.17.10 | 6 / 17 | |
| 3.17.9 | 6 / 17 | |
| 3.17.8 | 6 / 17 | |
| 3.17.7 | 6 / 17 | |
| 3.17.6 | 6 / 17 | |
| 3.17.5 | 6 / 17 | |
| 3.17.4 | 6 / 17 | |
| 3.17.3 | 6 / 17 | |
| 3.17.2 | 6 / 17 | |
| 3.17.1 | 6 / 17 | |
| 3.17.0 | 6 / 17 | |
| 3.16.0 | 6 / 17 | |
| 3.15.4 | 6 / 17 | |
| 3.15.3 | 6 / 17 | |
| 3.15.2 | 6 / 17 |
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.