@times-components/ad
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:pg | AI (typosquat): Scoped @times-components package; no relation to 'pg'; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @times-components package; no relation to 'qs'; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @times-components package; no relation to 'zod'; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @times-components package; no relation to 'ajv'; stable false positive. | ai |
Versions (showing 100 of 157)
| Version | Deps | Published |
|---|---|---|
| 2.24.15 | 4 / 21 | |
| 2.24.14 | 4 / 21 | |
| 2.24.13 | 4 / 21 | |
| 2.24.12 | 4 / 21 | |
| 2.24.11 | 4 / 21 | |
| 2.24.10 | 4 / 21 | |
| 2.24.9 | 4 / 21 | |
| 2.24.8 | 4 / 21 | |
| 2.24.7 | 4 / 21 | |
| 2.24.6 | 4 / 21 | |
| 2.24.5 | 4 / 21 | |
| 2.24.4 | 4 / 21 | |
| 2.24.3 | 4 / 21 | |
| 2.24.2 | 4 / 21 | |
| 2.24.1 | 4 / 21 | |
| 2.24.0 | 4 / 21 | |
| 2.23.30 | 4 / 21 | |
| 2.23.29 | 4 / 21 | |
| 2.23.28 | 4 / 21 | |
| 2.23.27 | 4 / 21 | |
| 2.23.26 | 4 / 21 | |
| 2.23.25 | 4 / 21 | |
| 2.23.24 | 4 / 21 | |
| 2.23.23 | 4 / 21 | |
| 2.23.22 | 4 / 21 | |
| 2.23.21 | 4 / 21 | |
| 2.23.20 | 4 / 21 | |
| 2.23.19 | 4 / 21 | |
| 2.23.18 | 4 / 21 | |
| 2.23.17 | 4 / 21 | |
| 2.23.16 | 4 / 21 | |
| 2.23.15 | 4 / 21 | |
| 2.23.14 | 4 / 21 | |
| 2.23.13 | 4 / 21 | |
| 2.23.12 | 4 / 21 | |
| 2.23.11 | 4 / 21 | |
| 2.23.10 | 4 / 21 | |
| 2.23.9 | 4 / 21 | |
| 2.23.8 | 4 / 21 | |
| 2.23.7 | 4 / 21 | |
| 2.23.6 | 4 / 21 | |
| 2.23.5 | 4 / 21 | |
| 2.23.4 | 4 / 21 | |
| 2.23.3 | 4 / 21 | |
| 2.23.2 | 4 / 21 | |
| 2.23.1 | 4 / 21 | |
| 2.23.0 | 4 / 21 | |
| 2.22.39 | 4 / 21 | |
| 2.22.38 | 4 / 21 | |
| 2.22.37 | 4 / 21 | |
| 2.22.36 | 4 / 21 | |
| 2.22.35 | 4 / 21 | |
| 2.22.34 | 4 / 21 | |
| 2.22.33 | 4 / 21 | |
| 2.22.32 | 4 / 21 | |
| 2.22.31 | 4 / 21 | |
| 2.22.30 | 4 / 21 | |
| 2.22.29 | 4 / 21 | |
| 2.22.28 | 4 / 21 | |
| 2.22.27 | 4 / 21 | |
| 2.22.26 | 4 / 21 | |
| 2.22.25 | 4 / 21 | |
| 2.22.24 | 4 / 21 | |
| 2.22.23 | 4 / 21 | |
| 2.22.22 | 4 / 21 | |
| 2.22.21 | 4 / 21 | |
| 2.22.20 | 4 / 21 | |
| 2.22.19 | 4 / 21 | |
| 2.22.18 | 4 / 21 | |
| 2.22.17 | 4 / 21 | |
| 2.22.16 | 4 / 21 | |
| 2.22.15 | 4 / 21 | |
| 2.22.14 | 4 / 21 | |
| 2.22.13 | 4 / 21 | |
| 2.22.12 | 4 / 21 | |
| 2.22.11 | 4 / 21 | |
| 2.22.10 | 4 / 21 | |
| 2.22.9 | 4 / 21 | |
| 2.22.8 | 4 / 21 | |
| 2.22.7 | 4 / 21 | |
| 2.22.6 | 4 / 21 | |
| 2.22.5 | 4 / 21 | |
| 2.22.4 | 4 / 21 | |
| 2.22.3 | 4 / 21 | |
| 2.22.2 | 4 / 21 | |
| 2.22.1 | 4 / 21 | |
| 2.22.0 | 4 / 21 | |
| 2.21.61 | 4 / 21 | |
| 2.21.60 | 4 / 21 | |
| 2.21.59 | 4 / 21 | |
| 2.21.58 | 4 / 21 | |
| 2.21.57 | 4 / 21 | |
| 2.21.56 | 4 / 21 | |
| 2.21.55 | 4 / 21 | |
| 2.21.54 | 4 / 21 | |
| 2.21.53 | 4 / 21 | |
| 2.21.52 | 4 / 21 | |
| 2.21.51 | 4 / 21 | |
| 2.21.50 | 4 / 21 | |
| 2.21.49 | 4 / 21 |
v2.22.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.13
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.