@times-components/ts-slices
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; sparse README/keywords are consistent across all 288 versions of this org's packages. | ai | |
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Same-org monorepo sibling dependency; not an external risk. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 1.10.62 | 5 / 15 | |
| 1.10.61 | 5 / 15 | |
| 1.10.60 | 5 / 15 | |
| 1.10.59 | 5 / 15 | |
| 1.10.58 | 5 / 15 | |
| 1.10.57 | 5 / 15 | |
| 1.10.56 | 5 / 15 | |
| 1.10.55 | 5 / 15 | |
| 1.10.54 | 5 / 15 | |
| 1.10.53 | 5 / 15 | |
| 1.10.52 | 5 / 15 | |
| 1.10.51 | 5 / 15 | |
| 1.10.50 | 5 / 15 | |
| 1.10.49 | 5 / 15 | |
| 1.10.48 | 5 / 15 | |
| 1.10.47 | 5 / 15 | |
| 1.10.46 | 5 / 15 | |
| 1.10.45 | 5 / 15 | |
| 1.10.44 | 5 / 15 | |
| 1.10.43 | 5 / 15 | |
| 1.10.42 | 5 / 15 | |
| 1.10.41 | 5 / 15 | |
| 1.10.40 | 5 / 15 | |
| 1.10.39 | 5 / 15 | |
| 1.10.38 | 5 / 15 | |
| 1.10.37 | 5 / 15 | |
| 1.10.36 | 5 / 15 | |
| 1.10.35 | 5 / 15 | |
| 1.10.34 | 5 / 15 | |
| 1.10.33 | 5 / 15 | |
| 1.10.32 | 5 / 15 | |
| 1.10.31 | 5 / 15 | |
| 1.10.30 | 5 / 15 | |
| 1.10.29 | 5 / 15 | |
| 1.10.28 | 5 / 15 | |
| 1.10.27 | 5 / 15 | |
| 1.10.26 | 5 / 15 | |
| 1.10.25 | 5 / 15 | |
| 1.10.24 | 5 / 15 | |
| 1.10.23 | 5 / 15 | |
| 1.10.22 | 5 / 15 | |
| 1.10.21 | 5 / 15 | |
| 1.10.20 | 5 / 15 | |
| 1.10.19 | 5 / 15 | |
| 1.10.18 | 5 / 15 | |
| 1.10.17 | 5 / 15 | |
| 1.10.16 | 5 / 15 | |
| 1.10.15 | 5 / 15 | |
| 1.10.14 | 5 / 15 | |
| 1.10.13 | 5 / 15 | |
| 1.10.12 | 5 / 15 | |
| 1.10.11 | 5 / 15 | |
| 1.10.10 | 5 / 15 | |
| 1.10.9 | 5 / 15 | |
| 1.10.8 | 5 / 15 | |
| 1.10.7 | 5 / 15 | |
| 1.10.6 | 5 / 15 | |
| 1.10.5 | 5 / 15 | |
| 1.10.4 | 5 / 15 | |
| 1.10.3 | 5 / 15 | |
| 1.10.2 | 5 / 15 | |
| 1.10.1 | 5 / 15 | |
| 1.10.0 | 5 / 15 | |
| 1.9.23 | 5 / 15 | |
| 1.9.22 | 5 / 15 | |
| 1.9.21 | 5 / 15 | |
| 1.9.20 | 5 / 15 | |
| 1.9.19 | 5 / 15 | |
| 1.9.18 | 5 / 15 | |
| 1.9.17 | 5 / 15 | |
| 1.9.16 | 5 / 15 | |
| 1.9.15 | 5 / 15 | |
| 1.9.14 | 5 / 15 | |
| 1.9.13 | 5 / 15 | |
| 1.9.12 | 5 / 15 | |
| 1.9.11 | 5 / 15 | |
| 1.9.10 | 5 / 15 | |
| 1.9.9 | 5 / 15 | |
| 1.9.8 | 5 / 15 | |
| 1.9.7 | 5 / 15 | |
| 1.9.6 | 5 / 15 | |
| 1.9.5 | 5 / 15 | |
| 1.9.4 | 5 / 15 | |
| 1.9.3 | 5 / 15 | |
| 1.9.2 | 5 / 15 | |
| 1.9.1 | 5 / 15 | |
| 1.9.0 | 5 / 15 | |
| 1.8.43 | 5 / 15 | |
| 1.8.42 | 5 / 15 | |
| 1.8.41 | 5 / 15 | |
| 1.8.40 | 5 / 15 | |
| 1.8.39 | 5 / 15 | |
| 1.8.38 | 5 / 15 | |
| 1.8.37 | 5 / 15 | |
| 1.8.36 | 5 / 15 | |
| 1.8.35 | 5 / 15 | |
| 1.8.34 | 5 / 15 | |
| 1.8.33 | 5 / 15 | |
| 1.8.32 | 5 / 15 | |
| 1.8.31 | 5 / 15 |
v1.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.