@tramvai/tinkoff-request-http-client-adapter
Interface implementation `HttpClient` from [@tramvai/http-client](references/libs/http-client.md) based on the library [@tinkoff/request](https://tinkoff.github.io/tinkoff-request/)
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tinkoff/request-plugin-cache-deduplicate | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-transform-url | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-circuit-breaker | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tramvai/http-client | AI (dependencies): First-party tramvai ecosystem dep; consistent across all versions of this adapter. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-log | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-validate | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-cache-etag | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-cache-memory | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-protocol-http | AI (dependencies): Core @tinkoff/request plugin; stable dependency for this adapter package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared in dependencies; phantom-dep is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Large monorepo package; provenance not used across the tramvai ecosystem. | ai |
Versions (showing 100 of 888)
| Version | Deps | Published |
|---|---|---|
| 0.11.242 | 14 / 0 | |
| 0.11.239 | 14 / 0 | |
| 0.11.235 | 14 / 0 | |
| 0.11.234 | 14 / 0 | |
| 0.11.233 | 14 / 0 | |
| 0.11.232 | 14 / 0 | |
| 0.11.229 | 14 / 0 | |
| 0.11.228 | 14 / 0 | |
| 0.11.225 | 14 / 0 | |
| 0.11.214 | 14 / 0 | |
| 0.11.191 | 14 / 0 | |
| 0.11.190 | 14 / 0 | |
| 0.11.189 | 14 / 0 | |
| 0.11.187 | 14 / 0 | |
| 0.11.184 | 14 / 0 | |
| 0.11.183 | 14 / 0 | |
| 0.11.181 | 14 / 0 | |
| 0.11.180 | 14 / 0 | |
| 0.11.178 | 14 / 0 | |
| 0.11.177 | 14 / 0 | |
| 0.11.176 | 14 / 0 | |
| 0.11.174 | 14 / 0 | |
| 0.11.173 | 14 / 0 | |
| 0.11.172 | 14 / 0 | |
| 0.11.171 | 14 / 0 | |
| 0.11.167 | 14 / 0 | |
| 0.11.166 | 14 / 0 | |
| 0.11.165 | 14 / 0 | |
| 0.11.164 | 14 / 0 | |
| 0.11.161 | 14 / 0 | |
| 0.11.160 | 14 / 0 | |
| 0.11.159 | 14 / 0 | |
| 0.11.157 | 14 / 0 | |
| 0.11.156 | 14 / 0 | |
| 0.11.154 | 14 / 0 | |
| 0.11.152 | 14 / 0 | |
| 0.11.150 | 14 / 0 | |
| 0.11.149 | 14 / 0 | |
| 0.11.146 | 14 / 0 | |
| 0.11.143 | 14 / 0 | |
| 0.11.142 | 14 / 0 | |
| 0.11.141 | 14 / 0 | |
| 0.11.140 | 14 / 0 | |
| 0.11.139 | 14 / 0 | |
| 0.11.138 | 14 / 0 | |
| 0.11.137 | 14 / 0 | |
| 0.11.136 | 14 / 0 | |
| 0.11.132 | 14 / 0 | |
| 0.11.130 | 14 / 0 | |
| 0.11.128 | 14 / 0 | |
| 0.11.126 | 14 / 0 | |
| 0.11.125 | 14 / 0 | |
| 0.11.124 | 14 / 0 | |
| 0.11.123 | 14 / 0 | |
| 0.11.121 | 14 / 0 | |
| 0.11.119 | 14 / 0 | |
| 0.11.116 | 14 / 0 | |
| 0.11.115 | 14 / 0 | |
| 0.11.112 | 14 / 0 | |
| 0.11.110 | 14 / 0 | |
| 0.11.109 | 14 / 0 | |
| 0.11.108 | 14 / 0 | |
| 0.11.104 | 14 / 0 | |
| 0.11.103 | 14 / 0 | |
| 0.11.100 | 14 / 0 | |
| 0.11.98 | 14 / 0 | |
| 0.11.97 | 14 / 0 | |
| 0.11.94 | 14 / 0 | |
| 0.11.91 | 14 / 0 | |
| 0.11.89 | 14 / 0 | |
| 0.11.87 | 14 / 0 | |
| 0.11.85 | 14 / 0 | |
| 0.11.84 | 14 / 0 | |
| 0.11.82 | 14 / 0 | |
| 0.11.81 | 14 / 0 | |
| 0.11.80 | 14 / 0 | |
| 0.11.79 | 14 / 0 | |
| 0.11.78 | 14 / 0 | |
| 0.11.77 | 14 / 0 | |
| 0.11.76 | 14 / 0 | |
| 0.11.75 | 14 / 0 | |
| 0.11.74 | 14 / 0 | |
| 0.11.73 | 14 / 0 | |
| 0.11.71 | 13 / 0 | |
| 0.11.65 | 13 / 0 | |
| 0.11.63 | 13 / 0 | |
| 0.11.62 | 13 / 0 | |
| 0.11.61 | 13 / 0 | |
| 0.11.60 | 13 / 0 | |
| 0.11.58 | 13 / 0 | |
| 0.11.57 | 13 / 0 | |
| 0.11.56 | 13 / 0 | |
| 0.11.55 | 13 / 0 | |
| 0.11.53 | 13 / 0 | |
| 0.11.52 | 13 / 0 | |
| 0.11.51 | 13 / 0 | |
| 0.11.46 | 13 / 0 | |
| 0.11.44 | 13 / 0 | |
| 0.11.43 | 13 / 0 | |
| 0.11.42 | 13 / 0 |
v0.11.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.235
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.234
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.233
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.232
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.229
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.228
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.225
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.191
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.187
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.181
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.150
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.149
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.146
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.142
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.139
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.136
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.