@times-components/article-topics
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established monorepo package; no provenance is consistent across all versions. | ai |
Versions (showing 100 of 166)
| Version | Deps | Published |
|---|---|---|
| 4.11.117 | 6 / 18 | |
| 4.11.116 | 6 / 18 | |
| 4.11.115 | 6 / 18 | |
| 4.11.114 | 6 / 18 | |
| 4.11.113 | 6 / 18 | |
| 4.11.112 | 6 / 18 | |
| 4.11.111 | 6 / 18 | |
| 4.11.110 | 6 / 18 | |
| 4.11.109 | 6 / 18 | |
| 4.11.108 | 6 / 18 | |
| 4.11.107 | 6 / 18 | |
| 4.11.106 | 6 / 18 | |
| 4.11.105 | 6 / 18 | |
| 4.11.104 | 6 / 18 | |
| 4.11.103 | 6 / 18 | |
| 4.11.102 | 6 / 18 | |
| 4.11.101 | 6 / 18 | |
| 4.11.100 | 6 / 18 | |
| 4.11.99 | 6 / 18 | |
| 4.11.98 | 6 / 18 | |
| 4.11.97 | 6 / 18 | |
| 4.11.96 | 6 / 18 | |
| 4.11.95 | 6 / 18 | |
| 4.11.94 | 6 / 18 | |
| 4.11.93 | 6 / 18 | |
| 4.11.92 | 6 / 18 | |
| 4.11.91 | 6 / 18 | |
| 4.11.90 | 6 / 18 | |
| 4.11.89 | 6 / 18 | |
| 4.11.88 | 6 / 18 | |
| 4.11.87 | 6 / 18 | |
| 4.11.86 | 6 / 18 | |
| 4.11.85 | 6 / 18 | |
| 4.11.84 | 6 / 18 | |
| 4.11.83 | 6 / 18 | |
| 4.11.82 | 6 / 18 | |
| 4.11.81 | 6 / 18 | |
| 4.11.80 | 6 / 18 | |
| 4.11.79 | 6 / 18 | |
| 4.11.78 | 6 / 18 | |
| 4.11.77 | 6 / 18 | |
| 4.11.76 | 6 / 18 | |
| 4.11.75 | 6 / 18 | |
| 4.11.74 | 6 / 18 | |
| 4.11.73 | 6 / 18 | |
| 4.11.72 | 6 / 18 | |
| 4.11.71 | 6 / 18 | |
| 4.11.70 | 6 / 18 | |
| 4.11.69 | 6 / 18 | |
| 4.11.68 | 6 / 18 | |
| 4.11.67 | 6 / 18 | |
| 4.11.66 | 6 / 18 | |
| 4.11.65 | 6 / 18 | |
| 4.11.64 | 6 / 18 | |
| 4.11.63 | 6 / 18 | |
| 4.11.62 | 6 / 18 | |
| 4.11.61 | 6 / 18 | |
| 4.11.60 | 6 / 18 | |
| 4.11.59 | 6 / 18 | |
| 4.11.58 | 6 / 18 | |
| 4.11.57 | 6 / 18 | |
| 4.11.56 | 6 / 18 | |
| 4.11.55 | 6 / 18 | |
| 4.11.54 | 6 / 18 | |
| 4.11.53 | 6 / 18 | |
| 4.11.52 | 6 / 18 | |
| 4.11.51 | 6 / 18 | |
| 4.11.50 | 6 / 18 | |
| 4.11.49 | 6 / 18 | |
| 4.11.48 | 6 / 18 | |
| 4.11.47 | 6 / 18 | |
| 4.11.46 | 6 / 18 | |
| 4.11.45 | 6 / 18 | |
| 4.11.44 | 6 / 18 | |
| 4.11.43 | 6 / 18 | |
| 4.11.42 | 6 / 18 | |
| 4.11.41 | 6 / 18 | |
| 4.11.40 | 6 / 18 | |
| 4.11.39 | 6 / 18 | |
| 4.11.38 | 6 / 18 | |
| 4.11.37 | 6 / 18 | |
| 4.11.36 | 6 / 18 | |
| 4.11.35 | 6 / 18 | |
| 4.11.34 | 6 / 18 | |
| 4.11.33 | 6 / 18 | |
| 4.11.32 | 6 / 18 | |
| 4.11.31 | 6 / 18 | |
| 4.11.30 | 6 / 18 | |
| 4.11.29 | 6 / 18 | |
| 4.11.28 | 6 / 18 | |
| 4.11.27 | 6 / 18 | |
| 4.11.26 | 6 / 18 | |
| 4.11.25 | 6 / 18 | |
| 4.11.24 | 6 / 18 | |
| 4.11.23 | 6 / 18 | |
| 4.11.22 | 6 / 18 | |
| 4.11.21 | 6 / 18 | |
| 4.11.20 | 6 / 18 | |
| 4.11.19 | 6 / 18 | |
| 4.11.18 | 6 / 18 |
v4.11.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.