@times-components/markup
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established monorepo package; provenance not part of their publish workflow across 743 versions. | ai | |
| phantom-deps | phantom-dep:@times-components/utils | AI (phantom-deps): Same-org monorepo dep; declared but re-exported rather than directly imported — stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@times-components/ts-styleguide | AI (phantom-deps): Same-org monorepo dep; declared but re-exported rather than directly imported — stable FP for this package. | ai |
Versions (showing 100 of 152)
| Version | Deps | Published |
|---|---|---|
| 3.9.62 | 2 / 18 | |
| 3.9.61 | 2 / 18 | |
| 3.9.60 | 2 / 18 | |
| 3.9.59 | 2 / 18 | |
| 3.9.58 | 2 / 18 | |
| 3.9.57 | 2 / 18 | |
| 3.9.56 | 2 / 18 | |
| 3.9.55 | 2 / 18 | |
| 3.9.54 | 2 / 18 | |
| 3.9.53 | 2 / 18 | |
| 3.9.52 | 2 / 18 | |
| 3.9.51 | 2 / 18 | |
| 3.9.50 | 2 / 18 | |
| 3.9.49 | 2 / 18 | |
| 3.9.48 | 2 / 18 | |
| 3.9.47 | 2 / 18 | |
| 3.9.46 | 2 / 18 | |
| 3.9.45 | 2 / 18 | |
| 3.9.44 | 2 / 18 | |
| 3.9.43 | 2 / 18 | |
| 3.9.42 | 2 / 18 | |
| 3.9.41 | 2 / 18 | |
| 3.9.40 | 2 / 18 | |
| 3.9.39 | 2 / 18 | |
| 3.9.38 | 2 / 18 | |
| 3.9.37 | 2 / 18 | |
| 3.9.36 | 2 / 18 | |
| 3.9.35 | 2 / 18 | |
| 3.9.34 | 2 / 18 | |
| 3.9.33 | 2 / 18 | |
| 3.9.32 | 2 / 18 | |
| 3.9.31 | 2 / 18 | |
| 3.9.30 | 2 / 18 | |
| 3.9.29 | 2 / 18 | |
| 3.9.28 | 2 / 18 | |
| 3.9.27 | 2 / 18 | |
| 3.9.26 | 2 / 18 | |
| 3.9.25 | 2 / 18 | |
| 3.9.24 | 2 / 18 | |
| 3.9.23 | 2 / 18 | |
| 3.9.22 | 2 / 18 | |
| 3.9.21 | 2 / 18 | |
| 3.9.20 | 2 / 18 | |
| 3.9.19 | 2 / 18 | |
| 3.9.18 | 2 / 18 | |
| 3.9.17 | 2 / 18 | |
| 3.9.16 | 2 / 18 | |
| 3.9.15 | 2 / 18 | |
| 3.9.14 | 2 / 18 | |
| 3.9.13 | 2 / 18 | |
| 3.9.12 | 2 / 18 | |
| 3.9.11 | 2 / 18 | |
| 3.9.10 | 2 / 18 | |
| 3.9.9 | 2 / 18 | |
| 3.9.8 | 2 / 18 | |
| 3.9.7 | 2 / 18 | |
| 3.9.6 | 2 / 18 | |
| 3.9.5 | 2 / 18 | |
| 3.9.4 | 2 / 18 | |
| 3.9.3 | 2 / 18 | |
| 3.9.2 | 2 / 18 | |
| 3.9.1 | 2 / 18 | |
| 3.9.0 | 2 / 18 | |
| 3.8.61 | 2 / 18 | |
| 3.8.60 | 2 / 18 | |
| 3.8.59 | 2 / 18 | |
| 3.8.58 | 2 / 18 | |
| 3.8.57 | 2 / 18 | |
| 3.8.56 | 2 / 18 | |
| 3.8.55 | 2 / 18 | |
| 3.8.54 | 2 / 18 | |
| 3.8.53 | 2 / 18 | |
| 3.8.52 | 2 / 18 | |
| 3.8.51 | 2 / 18 | |
| 3.8.50 | 2 / 18 | |
| 3.8.49 | 2 / 18 | |
| 3.8.48 | 2 / 18 | |
| 3.8.47 | 2 / 18 | |
| 3.8.46 | 2 / 18 | |
| 3.8.45 | 2 / 18 | |
| 3.8.44 | 2 / 18 | |
| 3.8.43 | 2 / 18 | |
| 3.8.42 | 2 / 18 | |
| 3.8.41 | 2 / 18 | |
| 3.8.40 | 2 / 18 | |
| 3.8.39 | 2 / 18 | |
| 3.8.38 | 2 / 18 | |
| 3.8.37 | 2 / 18 | |
| 3.8.36 | 2 / 18 | |
| 3.8.35 | 2 / 18 | |
| 3.8.34 | 2 / 18 | |
| 3.8.33 | 2 / 18 | |
| 3.8.32 | 2 / 18 | |
| 3.8.31 | 2 / 18 | |
| 3.8.30 | 2 / 18 | |
| 3.8.29 | 2 / 18 | |
| 3.8.28 | 2 / 18 | |
| 3.8.27 | 2 / 18 | |
| 3.8.26 | 2 / 18 | |
| 3.8.25 | 2 / 18 |
v3.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.42
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.8.41
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.8.40
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.8.39
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.8.38
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.8.37
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.8.36
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.8.35
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.8.34
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.8.33
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.8.32
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.8.31
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.8.30
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.8.29
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.8.28
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.8.27
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.8.26
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.8.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.