@times-components/article-main-video
Main Video 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/context | AI (phantom-deps): Same-org monorepo sibling; phantom-dep false positive for this package scope. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 130 approved packages; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 43 of 143)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 15 / 17 | |
| 1.14.0 | 15 / 17 | |
| 1.13.0 | 15 / 17 | |
| 1.12.0 | 15 / 17 | |
| 1.11.1 | 15 / 17 | |
| 1.11.0 | 15 / 17 | |
| 1.10.0 | 15 / 17 | |
| 1.9.1 | 15 / 17 | |
| 1.9.0 | 15 / 17 | |
| 1.8.0 | 15 / 17 | |
| 1.7.10 | 15 / 17 | |
| 1.7.9 | 15 / 17 | |
| 1.7.8 | 15 / 17 | |
| 1.7.7 | 15 / 17 | |
| 1.7.6 | 15 / 17 | |
| 1.7.5 | 15 / 17 | |
| 1.7.4 | 15 / 17 | |
| 1.7.3 | 15 / 17 | |
| 1.7.2 | 15 / 17 | |
| 1.7.1 | 15 / 17 | |
| 1.7.0 | 15 / 17 | |
| 1.6.2 | 15 / 17 | |
| 1.6.1 | 15 / 17 | |
| 1.6.0 | 15 / 17 | |
| 1.5.3 | 14 / 17 | |
| 1.5.2 | 14 / 17 | |
| 1.5.1 | 14 / 17 | |
| 1.5.0 | 14 / 17 | |
| 1.4.0 | 14 / 17 | |
| 1.3.3 | 14 / 17 | |
| 1.3.2 | 14 / 17 | |
| 1.3.1 | 14 / 17 | |
| 1.3.0 | 14 / 17 | |
| 1.2.0 | 14 / 17 | |
| 1.1.8 | 14 / 17 | |
| 1.1.7 | 14 / 17 | |
| 1.1.6 | 14 / 17 | |
| 1.1.5 | 14 / 17 | |
| 1.1.4 | 14 / 17 | |
| 1.1.3 | 14 / 17 | |
| 1.1.2 | 14 / 17 | |
| 1.1.1 | 14 / 17 | |
| 1.1.0 | 14 / 17 |
v1.5.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.
v1.5.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.
v1.5.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.
v1.4.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.
v1.3.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.
v1.3.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.
v1.3.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.
v1.3.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.
v1.2.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.
v1.1.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.