@times-components/author-profile
Author profile information along with a list of articles they have written
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/link | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/image | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/utils | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/gradient | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/tracking | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/pagination | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/responsive | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@times-components/ts-components | AI (dependencies): Sibling package from the same times-components monorepo; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established Times Components monorepo; provenance not used across the entire package family. | ai |
Versions (showing 100 of 567)
| Version | Deps | Published |
|---|---|---|
| 6.17.19 | 19 / 25 | |
| 6.17.18 | 19 / 25 | |
| 6.17.17 | 19 / 25 | |
| 6.17.16 | 19 / 25 | |
| 6.17.15 | 19 / 25 | |
| 6.17.14 | 19 / 25 | |
| 6.17.13 | 19 / 25 | |
| 6.17.12 | 19 / 25 | |
| 6.17.11 | 19 / 25 | |
| 6.17.10 | 19 / 25 | |
| 6.17.9 | 19 / 25 | |
| 6.17.8 | 19 / 25 | |
| 6.17.7 | 19 / 25 | |
| 6.17.6 | 19 / 25 | |
| 6.17.5 | 19 / 25 | |
| 6.17.4 | 19 / 25 | |
| 6.17.3 | 19 / 25 | |
| 6.17.2 | 19 / 25 | |
| 6.17.1 | 19 / 25 | |
| 6.17.0 | 19 / 25 | |
| 6.16.55 | 19 / 25 | |
| 6.16.54 | 19 / 25 | |
| 6.16.53 | 19 / 25 | |
| 6.16.52 | 19 / 25 | |
| 6.16.51 | 19 / 25 | |
| 6.16.50 | 19 / 25 | |
| 6.16.49 | 19 / 25 | |
| 6.16.48 | 19 / 25 | |
| 6.16.47 | 19 / 25 | |
| 6.16.46 | 19 / 25 | |
| 6.16.45 | 19 / 25 | |
| 6.16.44 | 19 / 25 | |
| 6.16.43 | 19 / 25 | |
| 6.16.42 | 19 / 25 | |
| 6.16.41 | 19 / 25 | |
| 6.16.40 | 19 / 25 | |
| 6.16.39 | 19 / 25 | |
| 6.16.38 | 19 / 25 | |
| 6.16.37 | 19 / 25 | |
| 6.16.36 | 19 / 25 | |
| 6.16.35 | 19 / 25 | |
| 6.16.34 | 19 / 25 | |
| 6.16.33 | 19 / 25 | |
| 6.16.32 | 19 / 25 | |
| 6.16.31 | 19 / 25 | |
| 6.16.30 | 19 / 25 | |
| 6.16.29 | 19 / 25 | |
| 6.16.28 | 19 / 25 | |
| 6.16.27 | 19 / 25 | |
| 6.16.26 | 19 / 25 | |
| 6.16.25 | 19 / 25 | |
| 6.16.24 | 19 / 25 | |
| 6.16.23 | 19 / 25 | |
| 6.16.22 | 19 / 25 | |
| 6.16.21 | 19 / 25 | |
| 6.16.20 | 19 / 25 | |
| 6.16.19 | 19 / 25 | |
| 6.16.18 | 19 / 25 | |
| 6.16.17 | 19 / 25 | |
| 6.16.16 | 19 / 25 | |
| 6.16.15 | 19 / 25 | |
| 6.16.14 | 19 / 25 | |
| 6.16.13 | 19 / 25 | |
| 6.16.12 | 19 / 25 | |
| 6.16.11 | 19 / 25 | |
| 6.16.10 | 19 / 25 | |
| 6.16.9 | 19 / 25 | |
| 6.16.8 | 19 / 25 | |
| 6.16.7 | 19 / 25 | |
| 6.16.6 | 19 / 25 | |
| 6.16.5 | 19 / 25 | |
| 6.16.4 | 19 / 25 | |
| 6.16.3 | 19 / 25 | |
| 6.16.2 | 19 / 25 | |
| 6.16.1 | 19 / 25 | |
| 6.16.0 | 19 / 25 | |
| 6.15.180 | 19 / 25 | |
| 6.15.179 | 19 / 25 | |
| 6.15.178 | 19 / 25 | |
| 6.15.177 | 19 / 25 | |
| 6.15.176 | 19 / 25 | |
| 6.15.175 | 19 / 25 | |
| 6.15.174 | 19 / 25 | |
| 6.15.173 | 19 / 25 | |
| 6.15.172 | 19 / 25 | |
| 6.15.171 | 19 / 25 | |
| 6.15.170 | 19 / 25 | |
| 6.15.169 | 19 / 25 | |
| 6.15.168 | 19 / 25 | |
| 6.15.167 | 19 / 25 | |
| 6.15.166 | 19 / 25 | |
| 6.15.165 | 19 / 25 | |
| 6.15.164 | 19 / 25 | |
| 6.15.163 | 19 / 25 | |
| 6.15.162 | 19 / 25 | |
| 6.15.161 | 19 / 25 | |
| 6.15.160 | 19 / 25 | |
| 6.15.159 | 19 / 25 | |
| 6.15.158 | 19 / 25 | |
| 6.15.157 | 19 / 25 |
v6.17.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.17.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.
v6.16.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.16.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.
v6.15.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.177
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.175
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.