@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 72 of 172)
| Version | Deps | Published |
|---|---|---|
| 4.15.38 | 7 / 17 | |
| 4.15.37 | 7 / 17 | |
| 4.15.36 | 7 / 17 | |
| 4.15.35 | 7 / 17 | |
| 4.15.34 | 7 / 17 | |
| 4.15.33 | 7 / 17 | |
| 4.15.32 | 7 / 17 | |
| 4.15.31 | 7 / 17 | |
| 4.15.30 | 7 / 17 | |
| 4.15.29 | 7 / 17 | |
| 4.15.28 | 7 / 17 | |
| 4.15.27 | 7 / 17 | |
| 4.15.26 | 7 / 17 | |
| 4.15.25 | 7 / 17 | |
| 4.15.24 | 7 / 17 | |
| 4.15.23 | 7 / 17 | |
| 4.15.22 | 7 / 17 | |
| 4.15.21 | 7 / 17 | |
| 4.15.20 | 7 / 17 | |
| 4.15.19 | 7 / 17 | |
| 4.15.18 | 7 / 17 | |
| 4.15.17 | 7 / 17 | |
| 4.15.16 | 7 / 17 | |
| 4.15.15 | 7 / 17 | |
| 4.15.14 | 7 / 17 | |
| 4.15.11 | 7 / 17 | |
| 4.15.10 | 7 / 17 | |
| 4.15.9 | 7 / 17 | |
| 4.15.8 | 7 / 17 | |
| 4.15.7 | 7 / 17 | |
| 4.15.6 | 7 / 17 | |
| 4.15.5 | 7 / 17 | |
| 4.15.3 | 7 / 17 | |
| 4.15.2 | 7 / 17 | |
| 4.15.1 | 7 / 17 | |
| 4.15.0 | 7 / 17 | |
| 4.14.12 | 7 / 17 | |
| 4.14.11 | 7 / 17 | |
| 4.14.10 | 7 / 17 | |
| 4.14.9 | 7 / 17 | |
| 4.14.8 | 7 / 17 | |
| 4.14.7 | 7 / 17 | |
| 4.14.6 | 7 / 17 | |
| 4.14.5 | 7 / 17 | |
| 4.14.4 | 7 / 17 | |
| 4.14.3 | 7 / 17 | |
| 4.14.2 | 7 / 17 | |
| 4.14.1 | 7 / 17 | |
| 4.14.0 | 7 / 17 | |
| 4.13.11 | 7 / 17 | |
| 4.13.10 | 7 / 17 | |
| 4.13.9 | 7 / 17 | |
| 4.13.8 | 7 / 17 | |
| 4.13.7 | 7 / 17 | |
| 4.13.6 | 7 / 17 | |
| 4.13.5 | 7 / 17 | |
| 4.13.4 | 7 / 17 | |
| 4.13.3 | 7 / 17 | |
| 4.13.2 | 7 / 17 | |
| 4.13.1 | 7 / 17 | |
| 4.13.0 | 7 / 17 | |
| 4.12.3 | 7 / 21 | |
| 4.12.2 | 7 / 21 | |
| 4.12.1 | 7 / 21 | |
| 4.12.0 | 7 / 21 | |
| 4.11.52 | 7 / 21 | |
| 4.11.51 | 7 / 21 | |
| 4.11.50 | 7 / 21 | |
| 4.11.49 | 7 / 21 | |
| 4.11.48 | 7 / 21 | |
| 4.11.47 | 7 / 21 | |
| 4.11.46 | 7 / 21 |
v4.15.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.