@times-components/article-magazine-comment
Magazine 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 sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@times-components/user-state | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 100 of 679)
| Version | Deps | Published |
|---|---|---|
| 3.95.16 | 16 / 19 | |
| 3.95.15 | 16 / 19 | |
| 3.95.14 | 16 / 19 | |
| 3.95.13 | 16 / 19 | |
| 3.95.12 | 16 / 19 | |
| 3.95.11 | 16 / 19 | |
| 3.95.10 | 16 / 19 | |
| 3.95.9 | 16 / 19 | |
| 3.95.8 | 16 / 19 | |
| 3.95.7 | 16 / 19 | |
| 3.95.6 | 16 / 19 | |
| 3.95.5 | 16 / 19 | |
| 3.95.4 | 16 / 19 | |
| 3.95.3 | 16 / 19 | |
| 3.95.2 | 16 / 19 | |
| 3.95.1 | 16 / 19 | |
| 3.95.0 | 16 / 19 | |
| 3.94.0 | 16 / 19 | |
| 3.93.5 | 16 / 19 | |
| 3.93.4 | 16 / 19 | |
| 3.93.3 | 16 / 19 | |
| 3.93.2 | 16 / 19 | |
| 3.93.1 | 16 / 19 | |
| 3.93.0 | 16 / 19 | |
| 3.92.5 | 16 / 19 | |
| 3.92.3 | 16 / 19 | |
| 3.92.2 | 16 / 19 | |
| 3.92.1 | 16 / 19 | |
| 3.92.0 | 16 / 19 | |
| 3.91.0 | 16 / 19 | |
| 3.90.15 | 16 / 19 | |
| 3.90.14 | 16 / 19 | |
| 3.90.13 | 16 / 19 | |
| 3.90.12 | 16 / 19 | |
| 3.90.11 | 16 / 19 | |
| 3.90.10 | 16 / 19 | |
| 3.90.9 | 16 / 19 | |
| 3.90.8 | 16 / 19 | |
| 3.90.7 | 16 / 19 | |
| 3.90.6 | 16 / 19 | |
| 3.90.5 | 16 / 19 | |
| 3.90.4 | 16 / 19 | |
| 3.90.3 | 16 / 19 | |
| 3.90.2 | 16 / 19 | |
| 3.90.1 | 16 / 19 | |
| 3.90.0 | 16 / 19 | |
| 3.89.19 | 16 / 19 | |
| 3.89.18 | 16 / 19 | |
| 3.89.17 | 16 / 19 | |
| 3.89.16 | 16 / 19 | |
| 3.89.15 | 16 / 19 | |
| 3.89.14 | 16 / 19 | |
| 3.89.13 | 16 / 19 | |
| 3.89.12 | 16 / 19 | |
| 3.89.11 | 16 / 19 | |
| 3.89.10 | 16 / 19 | |
| 3.89.9 | 16 / 19 | |
| 3.89.8 | 16 / 19 | |
| 3.89.7 | 16 / 19 | |
| 3.89.6 | 16 / 19 | |
| 3.89.5 | 16 / 19 | |
| 3.89.4 | 16 / 19 | |
| 3.89.3 | 16 / 19 | |
| 3.89.2 | 16 / 19 | |
| 3.89.1 | 16 / 19 | |
| 3.89.0 | 16 / 19 | |
| 3.88.3 | 16 / 19 | |
| 3.88.2 | 16 / 19 | |
| 3.88.1 | 16 / 19 | |
| 3.88.0 | 16 / 19 | |
| 3.87.6 | 16 / 19 | |
| 3.87.5 | 16 / 19 | |
| 3.87.4 | 16 / 19 | |
| 3.87.3 | 16 / 19 | |
| 3.87.2 | 16 / 19 | |
| 3.87.1 | 16 / 19 | |
| 3.87.0 | 16 / 19 | |
| 3.86.13 | 16 / 19 | |
| 3.86.12 | 16 / 19 | |
| 3.86.11 | 16 / 19 | |
| 3.86.10 | 16 / 19 | |
| 3.86.9 | 16 / 19 | |
| 3.86.8 | 16 / 19 | |
| 3.86.7 | 16 / 19 | |
| 3.86.6 | 16 / 19 | |
| 3.86.4 | 16 / 19 | |
| 3.86.3 | 16 / 19 | |
| 3.86.1 | 16 / 19 | |
| 3.86.0 | 16 / 19 | |
| 3.85.12 | 16 / 19 | |
| 3.85.11 | 16 / 19 | |
| 3.85.10 | 16 / 19 | |
| 3.85.9 | 16 / 19 | |
| 3.85.8 | 16 / 19 | |
| 3.85.7 | 16 / 19 | |
| 3.85.6 | 16 / 19 | |
| 3.85.5 | 16 / 19 | |
| 3.85.4 | 16 / 19 | |
| 3.85.3 | 16 / 19 | |
| 3.85.2 | 16 / 19 |
v3.93.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.93.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.88.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.88.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.