@times-components/video
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:vite | AI (typosquat): Scoped @times-components package from newsuk org; no relation to vite, Levenshtein match is spurious. | ai | |
| dependencies | unvetted-dep:@times-components/icons | AI (dependencies): Sibling package in the same newsuk/times-components monorepo; not an external unvetted dep. | ai | |
| dependencies | unvetted-dep:@times-components/image | AI (dependencies): Sibling package in the same newsuk/times-components monorepo. | ai | |
| dependencies | unvetted-dep:@times-components/utils | AI (dependencies): Sibling package in the same newsuk/times-components monorepo. | ai | |
| dependencies | unvetted-dep:@times-components/error-view | AI (dependencies): Sibling package in the same newsuk/times-components monorepo. | ai | |
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Sibling package in the same newsuk/times-components monorepo. | ai |
Versions (showing 100 of 172)
| Version | Deps | Published |
|---|---|---|
| 4.19.66 | 7 / 17 | |
| 4.19.65 | 7 / 17 | |
| 4.19.64 | 7 / 17 | |
| 4.19.63 | 7 / 17 | |
| 4.19.62 | 7 / 17 | |
| 4.19.61 | 7 / 17 | |
| 4.19.60 | 7 / 17 | |
| 4.19.59 | 7 / 17 | |
| 4.19.58 | 7 / 17 | |
| 4.19.57 | 7 / 17 | |
| 4.19.56 | 7 / 17 | |
| 4.19.55 | 7 / 17 | |
| 4.19.54 | 7 / 17 | |
| 4.19.53 | 7 / 17 | |
| 4.19.52 | 7 / 17 | |
| 4.19.51 | 7 / 17 | |
| 4.19.50 | 7 / 17 | |
| 4.19.49 | 7 / 17 | |
| 4.19.48 | 7 / 17 | |
| 4.19.47 | 7 / 17 | |
| 4.19.46 | 7 / 17 | |
| 4.19.45 | 7 / 17 | |
| 4.19.44 | 7 / 17 | |
| 4.19.43 | 7 / 17 | |
| 4.19.42 | 7 / 17 | |
| 4.19.41 | 7 / 17 | |
| 4.19.40 | 7 / 17 | |
| 4.19.39 | 7 / 17 | |
| 4.19.38 | 7 / 17 | |
| 4.19.37 | 7 / 17 | |
| 4.19.36 | 7 / 17 | |
| 4.19.35 | 7 / 17 | |
| 4.19.34 | 7 / 17 | |
| 4.19.33 | 7 / 17 | |
| 4.19.32 | 7 / 17 | |
| 4.19.31 | 7 / 17 | |
| 4.19.30 | 7 / 17 | |
| 4.19.29 | 7 / 17 | |
| 4.19.28 | 7 / 17 | |
| 4.19.27 | 7 / 17 | |
| 4.19.26 | 7 / 17 | |
| 4.19.25 | 7 / 17 | |
| 4.19.24 | 7 / 17 | |
| 4.19.23 | 7 / 17 | |
| 4.19.22 | 7 / 17 | |
| 4.19.21 | 7 / 17 | |
| 4.19.20 | 7 / 17 | |
| 4.19.19 | 7 / 17 | |
| 4.19.18 | 7 / 17 | |
| 4.19.17 | 7 / 17 | |
| 4.19.16 | 7 / 17 | |
| 4.19.15 | 7 / 17 | |
| 4.19.14 | 7 / 17 | |
| 4.19.13 | 7 / 17 | |
| 4.19.12 | 7 / 17 | |
| 4.19.11 | 7 / 17 | |
| 4.19.10 | 7 / 17 | |
| 4.19.9 | 7 / 17 | |
| 4.19.8 | 7 / 17 | |
| 4.19.7 | 7 / 17 | |
| 4.19.6 | 7 / 17 | |
| 4.19.5 | 7 / 17 | |
| 4.19.4 | 7 / 17 | |
| 4.19.3 | 7 / 17 | |
| 4.19.2 | 7 / 17 | |
| 4.19.1 | 7 / 17 | |
| 4.19.0 | 7 / 17 | |
| 4.18.26 | 7 / 17 | |
| 4.18.25 | 7 / 17 | |
| 4.18.24 | 7 / 17 | |
| 4.18.23 | 7 / 17 | |
| 4.18.22 | 7 / 17 | |
| 4.18.21 | 7 / 17 | |
| 4.18.20 | 7 / 17 | |
| 4.18.19 | 7 / 17 | |
| 4.18.18 | 7 / 17 | |
| 4.18.17 | 7 / 17 | |
| 4.18.16 | 7 / 17 | |
| 4.18.15 | 7 / 17 | |
| 4.18.14 | 7 / 17 | |
| 4.18.13 | 7 / 17 | |
| 4.18.12 | 7 / 17 | |
| 4.18.11 | 7 / 17 | |
| 4.18.10 | 7 / 17 | |
| 4.18.9 | 7 / 17 | |
| 4.18.8 | 7 / 17 | |
| 4.18.7 | 7 / 17 | |
| 4.18.6 | 7 / 17 | |
| 4.18.5 | 7 / 17 | |
| 4.18.4 | 7 / 17 | |
| 4.18.3 | 7 / 17 | |
| 4.18.2 | 7 / 17 | |
| 4.18.1 | 7 / 17 | |
| 4.18.0 | 7 / 17 | |
| 4.17.2 | 7 / 17 | |
| 4.17.1 | 7 / 17 | |
| 4.17.0 | 7 / 17 | |
| 4.16.0 | 7 / 17 | |
| 4.15.40 | 7 / 17 | |
| 4.15.39 | 7 / 17 |
v4.19.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.