@times-components/article-main-comment
Main Comment Article Template
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@times-components/ad | AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. | ai | |
| phantom-deps | phantom-dep:@times-components/responsive | AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. | ai | |
| phantom-deps | phantom-dep:@times-components/user-state | AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. | ai |
Versions (showing 100 of 717)
| Version | Deps | Published |
|---|---|---|
| 2.99.16 | 15 / 19 | |
| 2.99.15 | 15 / 19 | |
| 2.99.14 | 15 / 19 | |
| 2.99.13 | 15 / 19 | |
| 2.99.12 | 15 / 19 | |
| 2.99.11 | 15 / 19 | |
| 2.99.10 | 15 / 19 | |
| 2.99.9 | 15 / 19 | |
| 2.99.8 | 15 / 19 | |
| 2.99.7 | 15 / 19 | |
| 2.99.6 | 15 / 19 | |
| 2.99.5 | 15 / 19 | |
| 2.99.4 | 15 / 19 | |
| 2.99.3 | 15 / 19 | |
| 2.99.2 | 15 / 19 | |
| 2.99.1 | 15 / 19 | |
| 2.99.0 | 15 / 19 | |
| 2.98.0 | 15 / 19 | |
| 2.97.5 | 15 / 19 | |
| 2.97.4 | 15 / 19 | |
| 2.97.3 | 15 / 19 | |
| 2.97.2 | 15 / 19 | |
| 2.97.1 | 15 / 19 | |
| 2.97.0 | 15 / 19 | |
| 2.96.5 | 15 / 19 | |
| 2.96.3 | 15 / 19 | |
| 2.96.2 | 15 / 19 | |
| 2.96.1 | 15 / 19 | |
| 2.96.0 | 15 / 19 | |
| 2.95.0 | 15 / 19 | |
| 2.94.15 | 15 / 19 | |
| 2.94.14 | 15 / 19 | |
| 2.94.13 | 15 / 19 | |
| 2.94.12 | 15 / 19 | |
| 2.94.11 | 15 / 19 | |
| 2.94.10 | 15 / 19 | |
| 2.94.9 | 15 / 19 | |
| 2.94.8 | 15 / 19 | |
| 2.94.7 | 15 / 19 | |
| 2.94.6 | 15 / 19 | |
| 2.94.5 | 15 / 19 | |
| 2.94.4 | 15 / 19 | |
| 2.94.3 | 15 / 19 | |
| 2.94.2 | 15 / 19 | |
| 2.94.1 | 15 / 19 | |
| 2.94.0 | 15 / 19 | |
| 2.93.23 | 15 / 19 | |
| 2.93.22 | 15 / 19 | |
| 2.93.21 | 15 / 19 | |
| 2.93.20 | 15 / 19 | |
| 2.93.19 | 15 / 19 | |
| 2.93.18 | 15 / 19 | |
| 2.93.17 | 15 / 19 | |
| 2.93.16 | 15 / 19 | |
| 2.93.15 | 15 / 19 | |
| 2.93.14 | 15 / 19 | |
| 2.93.13 | 15 / 19 | |
| 2.93.12 | 15 / 19 | |
| 2.93.11 | 15 / 19 | |
| 2.93.10 | 15 / 19 | |
| 2.93.9 | 15 / 19 | |
| 2.93.8 | 15 / 19 | |
| 2.93.7 | 15 / 19 | |
| 2.93.6 | 15 / 19 | |
| 2.93.5 | 15 / 19 | |
| 2.93.4 | 15 / 19 | |
| 2.93.3 | 15 / 19 | |
| 2.93.2 | 15 / 19 | |
| 2.93.1 | 15 / 19 | |
| 2.93.0 | 15 / 19 | |
| 2.92.9 | 15 / 19 | |
| 2.92.8 | 15 / 19 | |
| 2.92.7 | 15 / 19 | |
| 2.92.6 | 15 / 19 | |
| 2.92.5 | 15 / 19 | |
| 2.92.4 | 15 / 19 | |
| 2.92.3 | 15 / 19 | |
| 2.92.2 | 15 / 19 | |
| 2.92.1 | 15 / 19 | |
| 2.92.0 | 15 / 19 | |
| 2.91.2 | 15 / 19 | |
| 2.91.1 | 15 / 19 | |
| 2.91.0 | 15 / 19 | |
| 2.90.0 | 15 / 19 | |
| 2.89.8 | 15 / 19 | |
| 2.89.7 | 15 / 19 | |
| 2.89.6 | 15 / 19 | |
| 2.89.4 | 15 / 19 | |
| 2.89.3 | 15 / 19 | |
| 2.89.1 | 15 / 19 | |
| 2.89.0 | 15 / 19 | |
| 2.88.12 | 15 / 19 | |
| 2.88.11 | 15 / 19 | |
| 2.88.10 | 15 / 19 | |
| 2.88.9 | 15 / 19 | |
| 2.88.8 | 15 / 19 | |
| 2.88.7 | 15 / 19 | |
| 2.88.6 | 15 / 19 | |
| 2.88.5 | 15 / 19 | |
| 2.88.4 | 15 / 19 |
v2.97.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.