@times-components/card
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @times-components/card is a legitimate Times Components monorepo package; Levenshtein match to 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:@times-components/responsive | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 100 of 166)
| Version | Deps | Published |
|---|---|---|
| 6.17.49 | 7 / 20 | |
| 6.17.48 | 7 / 20 | |
| 6.17.47 | 7 / 20 | |
| 6.17.46 | 7 / 20 | |
| 6.17.45 | 7 / 20 | |
| 6.17.44 | 7 / 20 | |
| 6.17.43 | 7 / 20 | |
| 6.17.42 | 7 / 20 | |
| 6.17.41 | 7 / 20 | |
| 6.17.40 | 7 / 20 | |
| 6.17.39 | 7 / 20 | |
| 6.17.38 | 7 / 20 | |
| 6.17.37 | 7 / 20 | |
| 6.17.36 | 7 / 20 | |
| 6.17.35 | 7 / 20 | |
| 6.17.34 | 7 / 20 | |
| 6.17.33 | 7 / 20 | |
| 6.17.32 | 7 / 20 | |
| 6.17.31 | 7 / 20 | |
| 6.17.30 | 7 / 20 | |
| 6.17.29 | 7 / 20 | |
| 6.17.28 | 7 / 20 | |
| 6.17.27 | 7 / 20 | |
| 6.17.26 | 7 / 20 | |
| 6.17.25 | 7 / 20 | |
| 6.17.24 | 7 / 20 | |
| 6.17.23 | 7 / 20 | |
| 6.17.22 | 7 / 20 | |
| 6.17.21 | 7 / 20 | |
| 6.17.20 | 7 / 20 | |
| 6.17.19 | 7 / 20 | |
| 6.17.18 | 7 / 20 | |
| 6.17.17 | 7 / 20 | |
| 6.17.16 | 7 / 20 | |
| 6.17.15 | 7 / 20 | |
| 6.17.14 | 7 / 20 | |
| 6.17.13 | 7 / 20 | |
| 6.17.12 | 7 / 20 | |
| 6.17.11 | 7 / 20 | |
| 6.17.10 | 7 / 20 | |
| 6.17.9 | 7 / 20 | |
| 6.17.8 | 7 / 20 | |
| 6.17.7 | 7 / 20 | |
| 6.17.6 | 7 / 20 | |
| 6.17.5 | 7 / 20 | |
| 6.17.4 | 7 / 20 | |
| 6.17.3 | 7 / 20 | |
| 6.17.2 | 7 / 20 | |
| 6.17.1 | 7 / 20 | |
| 6.17.0 | 7 / 20 | |
| 6.16.13 | 7 / 20 | |
| 6.16.12 | 7 / 20 | |
| 6.16.11 | 7 / 20 | |
| 6.16.10 | 7 / 20 | |
| 6.16.9 | 7 / 20 | |
| 6.16.8 | 7 / 20 | |
| 6.16.7 | 7 / 20 | |
| 6.16.6 | 7 / 20 | |
| 6.16.5 | 7 / 20 | |
| 6.16.4 | 7 / 20 | |
| 6.16.3 | 7 / 20 | |
| 6.16.2 | 7 / 20 | |
| 6.16.1 | 7 / 20 | |
| 6.16.0 | 7 / 20 | |
| 6.15.2 | 7 / 20 | |
| 6.15.1 | 7 / 20 | |
| 6.15.0 | 7 / 20 | |
| 6.14.21 | 7 / 20 | |
| 6.14.20 | 7 / 20 | |
| 6.14.19 | 7 / 20 | |
| 6.14.18 | 7 / 20 | |
| 6.14.17 | 7 / 20 | |
| 6.14.16 | 7 / 20 | |
| 6.14.15 | 7 / 20 | |
| 6.14.14 | 7 / 20 | |
| 6.14.13 | 7 / 20 | |
| 6.14.12 | 7 / 20 | |
| 6.14.11 | 7 / 20 | |
| 6.14.10 | 7 / 20 | |
| 6.14.9 | 7 / 20 | |
| 6.14.8 | 7 / 20 | |
| 6.14.7 | 7 / 20 | |
| 6.14.6 | 7 / 20 | |
| 6.14.5 | 7 / 20 | |
| 6.14.4 | 7 / 20 | |
| 6.14.3 | 7 / 20 | |
| 6.14.2 | 7 / 20 | |
| 6.14.1 | 7 / 20 | |
| 6.14.0 | 7 / 20 | |
| 6.13.7 | 7 / 20 | |
| 6.13.6 | 7 / 20 | |
| 6.13.5 | 7 / 20 | |
| 6.13.4 | 7 / 20 | |
| 6.13.3 | 7 / 20 | |
| 6.13.2 | 7 / 20 | |
| 6.13.1 | 7 / 20 | |
| 6.13.0 | 7 / 20 | |
| 6.12.25 | 7 / 20 | |
| 6.12.24 | 7 / 20 | |
| 6.12.23 | 7 / 20 |
v6.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.