@times-components/article-paragraph
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/article-skeleton | AI (phantom-deps): Same-org sibling package in times-components monorepo; consistent pattern with other accepted phantom deps in this package. | ai | |
| phantom-deps | phantom-dep:@times-components/context | AI (phantom-deps): Same-org monorepo dep; phantom-dep false positive common in monorepo setups. | ai | |
| phantom-deps | phantom-dep:@times-components/markup-forest | AI (phantom-deps): Same-org monorepo dep; phantom-dep false positive common in monorepo setups. | ai |
Versions (showing 100 of 605)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 5 / 17 | |
| 1.22.1 | 5 / 17 | |
| 1.22.0 | 5 / 17 | |
| 1.21.1 | 5 / 17 | |
| 1.21.0 | 5 / 17 | |
| 1.20.0 | 5 / 17 | |
| 1.19.2 | 5 / 17 | |
| 1.19.1 | 5 / 17 | |
| 1.19.0 | 5 / 17 | |
| 1.18.0 | 5 / 17 | |
| 1.17.0 | 5 / 17 | |
| 1.16.0 | 5 / 17 | |
| 1.15.0 | 5 / 17 | |
| 1.14.1 | 5 / 17 | |
| 1.14.0 | 5 / 17 | |
| 1.13.0 | 5 / 17 | |
| 1.12.1 | 5 / 17 | |
| 1.12.0 | 5 / 17 | |
| 1.11.1 | 5 / 17 | |
| 1.11.0 | 5 / 17 | |
| 1.10.0 | 5 / 17 | |
| 1.9.435 | 6 / 17 | |
| 1.9.434 | 6 / 17 | |
| 1.9.433 | 6 / 17 | |
| 1.9.432 | 6 / 17 | |
| 1.9.431 | 6 / 17 | |
| 1.9.430 | 6 / 17 | |
| 1.9.429 | 6 / 17 | |
| 1.9.428 | 6 / 17 | |
| 1.9.427 | 6 / 17 | |
| 1.9.426 | 6 / 17 | |
| 1.9.425 | 6 / 17 | |
| 1.9.424 | 6 / 17 | |
| 1.9.423 | 6 / 17 | |
| 1.9.422 | 6 / 17 | |
| 1.9.421 | 6 / 17 | |
| 1.9.420 | 6 / 17 | |
| 1.9.419 | 6 / 17 | |
| 1.9.418 | 6 / 17 | |
| 1.9.417 | 6 / 17 | |
| 1.9.416 | 6 / 17 | |
| 1.9.415 | 6 / 17 | |
| 1.9.414 | 6 / 17 | |
| 1.9.413 | 6 / 17 | |
| 1.9.412 | 6 / 17 | |
| 1.9.411 | 6 / 17 | |
| 1.9.410 | 6 / 17 | |
| 1.9.409 | 6 / 17 | |
| 1.9.408 | 6 / 17 | |
| 1.9.407 | 6 / 17 | |
| 1.9.406 | 6 / 17 | |
| 1.9.405 | 6 / 17 | |
| 1.9.404 | 6 / 17 | |
| 1.9.403 | 6 / 17 | |
| 1.9.402 | 6 / 17 | |
| 1.9.401 | 6 / 17 | |
| 1.9.400 | 6 / 17 | |
| 1.9.398 | 6 / 17 | |
| 1.9.397 | 6 / 17 | |
| 1.9.396 | 6 / 17 | |
| 1.9.395 | 6 / 17 | |
| 1.9.394 | 6 / 17 | |
| 1.9.393 | 6 / 17 | |
| 1.9.392 | 6 / 17 | |
| 1.9.391 | 6 / 17 | |
| 1.9.390 | 6 / 17 | |
| 1.9.389 | 6 / 17 | |
| 1.9.388 | 6 / 17 | |
| 1.9.387 | 6 / 17 | |
| 1.9.386 | 6 / 17 | |
| 1.9.385 | 6 / 17 | |
| 1.9.384 | 6 / 17 | |
| 1.9.383 | 6 / 17 | |
| 1.9.382 | 6 / 17 | |
| 1.9.381 | 6 / 17 | |
| 1.9.380 | 6 / 17 | |
| 1.9.379 | 6 / 17 | |
| 1.9.378 | 6 / 17 | |
| 1.9.377 | 6 / 17 | |
| 1.9.376 | 6 / 17 | |
| 1.9.375 | 6 / 17 | |
| 1.9.374 | 6 / 17 | |
| 1.9.373 | 6 / 17 | |
| 1.9.372 | 6 / 17 | |
| 1.9.371 | 6 / 17 | |
| 1.9.370 | 6 / 17 | |
| 1.9.369 | 6 / 17 | |
| 1.9.368 | 6 / 17 | |
| 1.9.367 | 6 / 17 | |
| 1.9.366 | 6 / 17 | |
| 1.9.365 | 6 / 17 | |
| 1.9.364 | 6 / 17 | |
| 1.9.363 | 6 / 17 | |
| 1.9.362 | 6 / 17 | |
| 1.9.361 | 6 / 17 | |
| 1.9.360 | 6 / 17 | |
| 1.9.359 | 6 / 17 | |
| 1.9.358 | 6 / 17 | |
| 1.9.357 | 6 / 17 | |
| 1.9.356 | 6 / 17 |
v1.9.403
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.402
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.401
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.398
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.397
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.396
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.395
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.394
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.393
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.392
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.391
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.388
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.384
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.383
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.382
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.381
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.380
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.379
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.378
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.376
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.370
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.366
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.365
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.364
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.359
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.358
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.357
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.356
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.