@times-components/article-main-standard
Main Standard 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/article-skeleton | AI (dependencies): Sibling package from the same times-components monorepo; not an independent third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not used across the @times-components ecosystem. | ai |
Versions (showing 100 of 677)
| Version | Deps | Published |
|---|---|---|
| 3.108.18 | 17 / 18 | |
| 3.108.17 | 17 / 18 | |
| 3.108.16 | 17 / 18 | |
| 3.108.15 | 17 / 18 | |
| 3.108.14 | 17 / 18 | |
| 3.108.13 | 17 / 18 | |
| 3.108.12 | 17 / 18 | |
| 3.108.11 | 17 / 18 | |
| 3.108.10 | 17 / 18 | |
| 3.108.9 | 17 / 18 | |
| 3.108.8 | 17 / 18 | |
| 3.108.7 | 17 / 18 | |
| 3.108.6 | 17 / 18 | |
| 3.108.5 | 17 / 18 | |
| 3.108.4 | 17 / 18 | |
| 3.108.3 | 17 / 18 | |
| 3.108.2 | 17 / 18 | |
| 3.108.1 | 17 / 18 | |
| 3.108.0 | 17 / 18 | |
| 3.107.0 | 17 / 18 | |
| 3.106.5 | 17 / 18 | |
| 3.106.4 | 17 / 18 | |
| 3.106.3 | 17 / 18 | |
| 3.106.2 | 17 / 18 | |
| 3.106.1 | 17 / 18 | |
| 3.106.0 | 17 / 18 | |
| 3.105.5 | 17 / 18 | |
| 3.105.3 | 17 / 18 | |
| 3.105.2 | 17 / 18 | |
| 3.105.1 | 17 / 18 | |
| 3.105.0 | 17 / 18 | |
| 3.104.0 | 17 / 18 | |
| 3.103.8 | 17 / 18 | |
| 3.103.7 | 17 / 18 | |
| 3.103.6 | 17 / 18 | |
| 3.103.5 | 17 / 18 | |
| 3.103.4 | 17 / 18 | |
| 3.103.3 | 17 / 18 | |
| 3.103.2 | 17 / 18 | |
| 3.103.1 | 17 / 18 | |
| 3.103.0 | 17 / 18 | |
| 3.102.6 | 17 / 18 | |
| 3.102.5 | 17 / 18 | |
| 3.102.4 | 17 / 18 | |
| 3.102.3 | 17 / 18 | |
| 3.102.2 | 17 / 18 | |
| 3.102.1 | 17 / 18 | |
| 3.102.0 | 17 / 18 | |
| 3.101.19 | 17 / 18 | |
| 3.101.18 | 17 / 18 | |
| 3.101.17 | 17 / 18 | |
| 3.101.16 | 17 / 18 | |
| 3.101.15 | 17 / 18 | |
| 3.101.14 | 17 / 18 | |
| 3.101.13 | 17 / 18 | |
| 3.101.12 | 17 / 18 | |
| 3.101.11 | 17 / 18 | |
| 3.101.10 | 17 / 18 | |
| 3.101.9 | 17 / 18 | |
| 3.101.8 | 17 / 18 | |
| 3.101.7 | 17 / 18 | |
| 3.101.6 | 17 / 18 | |
| 3.101.5 | 17 / 18 | |
| 3.101.4 | 17 / 18 | |
| 3.101.3 | 17 / 18 | |
| 3.101.2 | 17 / 18 | |
| 3.101.1 | 17 / 18 | |
| 3.101.0 | 17 / 18 | |
| 3.100.3 | 17 / 18 | |
| 3.100.2 | 17 / 18 | |
| 3.100.1 | 17 / 18 | |
| 3.100.0 | 17 / 18 | |
| 3.99.9 | 17 / 18 | |
| 3.99.8 | 17 / 18 | |
| 3.99.7 | 17 / 18 | |
| 3.99.6 | 17 / 18 | |
| 3.99.5 | 17 / 18 | |
| 3.99.4 | 17 / 18 | |
| 3.99.3 | 17 / 18 | |
| 3.99.2 | 17 / 18 | |
| 3.99.1 | 17 / 18 | |
| 3.99.0 | 17 / 18 | |
| 3.98.9 | 17 / 18 | |
| 3.98.8 | 17 / 18 | |
| 3.98.7 | 17 / 18 | |
| 3.98.6 | 17 / 18 | |
| 3.98.4 | 17 / 18 | |
| 3.98.3 | 17 / 18 | |
| 3.98.1 | 17 / 18 | |
| 3.98.0 | 17 / 18 | |
| 3.97.12 | 17 / 18 | |
| 3.97.11 | 17 / 18 | |
| 3.97.10 | 17 / 18 | |
| 3.97.9 | 17 / 18 | |
| 3.97.8 | 17 / 18 | |
| 3.97.7 | 17 / 18 | |
| 3.97.6 | 17 / 18 | |
| 3.97.5 | 17 / 18 | |
| 3.97.4 | 17 / 18 | |
| 3.97.3 | 17 / 18 |
v3.106.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.106.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.