@times-components/article-list
Paginated list of articles
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/ad | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/card | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/link | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/image | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/utils | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/button | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/context | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/tracking | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/error-view | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| dependencies | unvetted-dep:@times-components/pagination | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @times-components versions. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 51 of 95)
| Version | Deps | Published |
|---|---|---|
| 9.20.100 | 16 / 26 | |
| 9.20.99 | 16 / 26 | |
| 9.20.98 | 16 / 26 | |
| 9.20.97 | 16 / 26 | |
| 9.20.96 | 16 / 26 | |
| 9.20.94 | 16 / 26 | |
| 9.20.93 | 16 / 26 | |
| 9.20.92 | 16 / 26 | |
| 9.20.91 | 16 / 26 | |
| 9.20.90 | 16 / 26 | |
| 9.20.89 | 16 / 26 | |
| 9.20.88 | 16 / 26 | |
| 9.20.87 | 16 / 26 | |
| 9.20.86 | 16 / 26 | |
| 9.20.85 | 16 / 26 | |
| 9.20.84 | 16 / 26 | |
| 9.20.83 | 16 / 26 | |
| 9.20.82 | 16 / 26 | |
| 9.20.81 | 16 / 26 | |
| 9.20.80 | 16 / 26 | |
| 9.20.79 | 16 / 26 | |
| 9.20.78 | 16 / 26 | |
| 9.20.77 | 16 / 26 | |
| 9.20.76 | 16 / 26 | |
| 9.20.75 | 16 / 26 | |
| 9.20.74 | 16 / 26 | |
| 9.20.71 | 16 / 26 | |
| 9.20.70 | 16 / 26 | |
| 9.20.69 | 16 / 26 | |
| 9.20.68 | 16 / 26 | |
| 9.20.67 | 16 / 26 | |
| 9.20.66 | 16 / 26 | |
| 9.20.65 | 16 / 26 | |
| 9.20.64 | 16 / 26 | |
| 9.20.63 | 16 / 26 | |
| 9.20.62 | 16 / 26 | |
| 9.20.61 | 16 / 26 | |
| 9.20.60 | 16 / 26 | |
| 9.20.59 | 16 / 26 | |
| 9.20.58 | 16 / 26 | |
| 9.20.57 | 16 / 26 | |
| 9.20.56 | 16 / 26 | |
| 9.20.55 | 16 / 26 | |
| 9.20.54 | 16 / 26 | |
| 9.20.53 | 16 / 26 | |
| 9.20.52 | 16 / 26 | |
| 9.20.51 | 16 / 26 | |
| 9.20.50 | 16 / 26 | |
| 9.20.49 | 16 / 26 | |
| 9.20.48 | 16 / 26 | |
| 9.20.47 | 16 / 26 |
v9.20.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.