@times-components/article-extras
Extra information components at the bottom of the articles, such as topics, related articles and comments
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/utils | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/button | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/context | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/user-state | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/ts-components | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/article-comments | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/related-articles | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| dependencies | unvetted-dep:@times-components/save-and-share-bar | AI (dependencies): Same-monorepo sibling dep; stable false positive for @times-components packages. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; no provenance is expected for this package family. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.41.83 | 13 / 15 | |
| 0.41.82 | 13 / 15 | |
| 0.41.81 | 13 / 15 | |
| 0.41.80 | 13 / 15 | |
| 0.41.79 | 13 / 15 | |
| 0.41.77 | 13 / 15 | |
| 0.41.76 | 13 / 15 | |
| 0.41.75 | 13 / 15 | |
| 0.41.74 | 13 / 15 | |
| 0.41.73 | 13 / 15 | |
| 0.41.72 | 13 / 15 | |
| 0.41.71 | 13 / 15 | |
| 0.41.70 | 13 / 15 | |
| 0.41.69 | 13 / 15 | |
| 0.41.68 | 13 / 15 | |
| 0.41.67 | 13 / 15 | |
| 0.41.66 | 13 / 15 | |
| 0.41.65 | 13 / 15 | |
| 0.41.64 | 13 / 15 | |
| 0.41.63 | 13 / 15 | |
| 0.41.29 | 13 / 15 | |
| 0.41.28 | 13 / 15 | |
| 0.41.27 | 13 / 15 | |
| 0.41.26 | 13 / 15 | |
| 0.41.25 | 13 / 15 | |
| 0.41.24 | 13 / 15 | |
| 0.41.23 | 13 / 15 | |
| 0.41.22 | 13 / 15 | |
| 0.41.21 | 13 / 15 | |
| 0.41.20 | 13 / 15 | |
| 0.41.19 | 13 / 15 | |
| 0.41.18 | 13 / 15 | |
| 0.41.17 | 13 / 15 | |
| 0.41.16 | 13 / 15 | |
| 0.41.15 | 13 / 15 | |
| 0.41.14 | 13 / 15 | |
| 0.41.13 | 13 / 15 | |
| 0.41.12 | 13 / 15 | |
| 0.41.11 | 13 / 15 | |
| 0.41.10 | 13 / 15 | |
| 0.41.9 | 13 / 15 | |
| 0.41.8 | 13 / 15 | |
| 0.41.7 | 13 / 15 | |
| 0.41.6 | 13 / 15 | |
| 0.41.5 | 13 / 15 | |
| 0.41.4 | 13 / 15 | |
| 0.41.3 | 13 / 15 | |
| 0.41.2 | 13 / 15 | |
| 0.41.1 | 13 / 15 | |
| 0.41.0 | 13 / 15 | |
| 0.40.1 | 13 / 15 |
v0.41.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.