@times-components/icons
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:cors | AI (typosquat): Scoped @times-components/* package from newsuk monorepo; no relation to 'cors'. | ai |
Versions (showing 100 of 157)
| Version | Deps | Published |
|---|---|---|
| 2.23.63 | 4 / 17 | |
| 2.23.62 | 4 / 17 | |
| 2.23.61 | 4 / 17 | |
| 2.23.60 | 4 / 17 | |
| 2.23.59 | 4 / 17 | |
| 2.23.58 | 4 / 17 | |
| 2.23.57 | 4 / 17 | |
| 2.23.56 | 4 / 17 | |
| 2.23.55 | 4 / 17 | |
| 2.23.54 | 4 / 17 | |
| 2.23.53 | 4 / 17 | |
| 2.23.52 | 4 / 17 | |
| 2.23.51 | 4 / 17 | |
| 2.23.50 | 4 / 17 | |
| 2.23.49 | 4 / 17 | |
| 2.23.48 | 4 / 17 | |
| 2.23.47 | 4 / 17 | |
| 2.23.46 | 4 / 17 | |
| 2.23.45 | 4 / 17 | |
| 2.23.44 | 4 / 17 | |
| 2.23.43 | 4 / 17 | |
| 2.23.42 | 4 / 17 | |
| 2.23.41 | 4 / 17 | |
| 2.23.40 | 4 / 17 | |
| 2.23.39 | 4 / 17 | |
| 2.23.38 | 4 / 17 | |
| 2.23.37 | 4 / 17 | |
| 2.23.36 | 4 / 17 | |
| 2.23.35 | 4 / 17 | |
| 2.23.34 | 4 / 17 | |
| 2.23.33 | 4 / 17 | |
| 2.23.32 | 4 / 17 | |
| 2.23.31 | 4 / 17 | |
| 2.23.30 | 4 / 17 | |
| 2.23.29 | 4 / 17 | |
| 2.23.28 | 4 / 17 | |
| 2.23.27 | 4 / 17 | |
| 2.23.26 | 4 / 17 | |
| 2.23.25 | 4 / 17 | |
| 2.23.24 | 4 / 17 | |
| 2.23.23 | 4 / 17 | |
| 2.23.22 | 4 / 17 | |
| 2.23.21 | 4 / 17 | |
| 2.23.20 | 4 / 17 | |
| 2.23.19 | 4 / 17 | |
| 2.23.18 | 4 / 17 | |
| 2.23.17 | 4 / 17 | |
| 2.23.16 | 4 / 17 | |
| 2.23.15 | 4 / 17 | |
| 2.23.14 | 4 / 17 | |
| 2.23.13 | 4 / 17 | |
| 2.23.12 | 4 / 17 | |
| 2.23.11 | 4 / 17 | |
| 2.23.10 | 4 / 17 | |
| 2.23.9 | 4 / 17 | |
| 2.23.8 | 4 / 17 | |
| 2.23.7 | 4 / 17 | |
| 2.23.6 | 4 / 17 | |
| 2.23.5 | 4 / 17 | |
| 2.23.4 | 4 / 17 | |
| 2.23.3 | 4 / 17 | |
| 2.23.2 | 4 / 17 | |
| 2.23.1 | 4 / 17 | |
| 2.23.0 | 4 / 17 | |
| 2.22.12 | 4 / 17 | |
| 2.22.11 | 4 / 17 | |
| 2.22.10 | 4 / 17 | |
| 2.22.9 | 4 / 17 | |
| 2.22.8 | 4 / 17 | |
| 2.22.7 | 4 / 17 | |
| 2.22.6 | 4 / 17 | |
| 2.22.5 | 4 / 17 | |
| 2.22.4 | 4 / 17 | |
| 2.22.3 | 4 / 17 | |
| 2.22.2 | 4 / 17 | |
| 2.22.1 | 4 / 17 | |
| 2.22.0 | 4 / 17 | |
| 2.21.27 | 4 / 17 | |
| 2.21.26 | 4 / 17 | |
| 2.21.25 | 4 / 17 | |
| 2.21.24 | 4 / 17 | |
| 2.21.23 | 4 / 17 | |
| 2.21.22 | 4 / 17 | |
| 2.21.21 | 4 / 17 | |
| 2.21.20 | 4 / 17 | |
| 2.21.19 | 4 / 17 | |
| 2.21.18 | 4 / 17 | |
| 2.21.17 | 4 / 17 | |
| 2.21.16 | 4 / 17 | |
| 2.21.15 | 4 / 17 | |
| 2.21.14 | 4 / 17 | |
| 2.21.13 | 4 / 17 | |
| 2.21.12 | 4 / 17 | |
| 2.21.11 | 4 / 17 | |
| 2.21.10 | 4 / 17 | |
| 2.21.9 | 4 / 17 | |
| 2.21.8 | 4 / 17 | |
| 2.21.7 | 4 / 17 | |
| 2.21.6 | 4 / 17 | |
| 2.21.5 | 4 / 17 |
v2.23.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.