@times-components/ts-styleguide
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@times-components/link | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 100 of 149)
| Version | Deps | Published |
|---|---|---|
| 1.56.41 | 4 / 10 | |
| 1.56.40 | 4 / 10 | |
| 1.56.39 | 4 / 10 | |
| 1.56.38 | 4 / 10 | |
| 1.56.37 | 4 / 10 | |
| 1.56.36 | 4 / 10 | |
| 1.56.35 | 4 / 10 | |
| 1.56.34 | 4 / 10 | |
| 1.56.33 | 4 / 10 | |
| 1.56.32 | 4 / 10 | |
| 1.56.31 | 4 / 10 | |
| 1.56.30 | 4 / 10 | |
| 1.56.29 | 4 / 10 | |
| 1.56.28 | 4 / 10 | |
| 1.56.27 | 4 / 10 | |
| 1.56.26 | 4 / 10 | |
| 1.56.25 | 4 / 10 | |
| 1.56.24 | 4 / 10 | |
| 1.56.23 | 4 / 10 | |
| 1.56.22 | 4 / 10 | |
| 1.56.21 | 4 / 10 | |
| 1.56.20 | 4 / 10 | |
| 1.56.19 | 4 / 10 | |
| 1.56.18 | 4 / 10 | |
| 1.56.17 | 4 / 10 | |
| 1.56.16 | 4 / 10 | |
| 1.56.15 | 4 / 10 | |
| 1.56.14 | 4 / 10 | |
| 1.56.13 | 4 / 10 | |
| 1.56.12 | 4 / 10 | |
| 1.56.11 | 4 / 10 | |
| 1.56.10 | 4 / 10 | |
| 1.56.9 | 4 / 10 | |
| 1.56.8 | 4 / 10 | |
| 1.56.7 | 4 / 10 | |
| 1.56.6 | 4 / 10 | |
| 1.56.5 | 4 / 10 | |
| 1.56.4 | 4 / 10 | |
| 1.56.3 | 4 / 10 | |
| 1.56.2 | 4 / 10 | |
| 1.56.1 | 4 / 10 | |
| 1.56.0 | 4 / 10 | |
| 1.55.1 | 4 / 10 | |
| 1.55.0 | 4 / 10 | |
| 1.54.1 | 4 / 10 | |
| 1.54.0 | 4 / 10 | |
| 1.53.1 | 4 / 10 | |
| 1.53.0 | 4 / 10 | |
| 1.52.2 | 4 / 10 | |
| 1.52.1 | 4 / 10 | |
| 1.52.0 | 4 / 10 | |
| 1.51.6 | 4 / 10 | |
| 1.51.5 | 4 / 10 | |
| 1.51.4 | 4 / 10 | |
| 1.51.3 | 4 / 10 | |
| 1.51.2 | 4 / 10 | |
| 1.51.1 | 4 / 10 | |
| 1.51.0 | 4 / 10 | |
| 1.50.37 | 4 / 10 | |
| 1.50.36 | 4 / 10 | |
| 1.50.35 | 4 / 10 | |
| 1.50.34 | 4 / 10 | |
| 1.50.33 | 4 / 10 | |
| 1.50.32 | 4 / 10 | |
| 1.50.31 | 4 / 10 | |
| 1.50.30 | 4 / 10 | |
| 1.50.29 | 4 / 10 | |
| 1.50.28 | 4 / 10 | |
| 1.50.27 | 4 / 10 | |
| 1.50.26 | 4 / 10 | |
| 1.50.25 | 4 / 10 | |
| 1.50.24 | 4 / 10 | |
| 1.50.23 | 4 / 10 | |
| 1.50.22 | 4 / 10 | |
| 1.50.21 | 4 / 10 | |
| 1.50.20 | 4 / 10 | |
| 1.50.19 | 4 / 10 | |
| 1.50.18 | 4 / 10 | |
| 1.50.17 | 4 / 10 | |
| 1.50.16 | 4 / 10 | |
| 1.50.15 | 4 / 10 | |
| 1.50.14 | 4 / 10 | |
| 1.50.13 | 4 / 10 | |
| 1.50.12 | 4 / 10 | |
| 1.50.11 | 4 / 10 | |
| 1.50.10 | 4 / 10 | |
| 1.50.9 | 4 / 10 | |
| 1.50.8 | 4 / 10 | |
| 1.50.7 | 4 / 10 | |
| 1.50.6 | 4 / 10 | |
| 1.50.5 | 4 / 10 | |
| 1.50.4 | 4 / 10 | |
| 1.50.3 | 4 / 10 | |
| 1.50.2 | 4 / 10 | |
| 1.50.1 | 4 / 10 | |
| 1.50.0 | 4 / 10 | |
| 1.49.0 | 4 / 10 | |
| 1.48.4 | 4 / 10 | |
| 1.48.3 | 4 / 10 | |
| 1.48.2 | 4 / 10 |
v1.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.