@ottocode/api
Type-safe API client for ottocode server
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): False positive: '@ottocode/api' is a scoped package; the edit distance is computed against the bare 'api' suffix, not the full name. No impersonation of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): False positive: edit distance is against the 'api' suffix of a scoped package. No impersonation of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: edit distance is against the 'api' suffix of a scoped package. No impersonation of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): False positive: edit distance is against the 'api' suffix of a scoped package. No impersonation of ajv. | ai |
Versions (showing 100 of 123)
| Version | Deps | Published |
|---|---|---|
| 0.1.300 | 2 / 3 | |
| 0.1.299 | 2 / 3 | |
| 0.1.298 | 2 / 3 | |
| 0.1.297 | 2 / 3 | |
| 0.1.296 | 2 / 3 | |
| 0.1.295 | 2 / 3 | |
| 0.1.294 | 2 / 3 | |
| 0.1.293 | 2 / 3 | |
| 0.1.292 | 2 / 3 | |
| 0.1.291 | 2 / 3 | |
| 0.1.290 | 2 / 3 | |
| 0.1.289 | 2 / 3 | |
| 0.1.288 | 2 / 3 | |
| 0.1.287 | 2 / 3 | |
| 0.1.286 | 2 / 3 | |
| 0.1.285 | 2 / 3 | |
| 0.1.284 | 2 / 3 | |
| 0.1.283 | 2 / 3 | |
| 0.1.282 | 2 / 3 | |
| 0.1.281 | 2 / 3 | |
| 0.1.280 | 2 / 3 | |
| 0.1.279 | 2 / 3 | |
| 0.1.278 | 2 / 3 | |
| 0.1.277 | 2 / 3 | |
| 0.1.276 | 2 / 3 | |
| 0.1.275 | 2 / 3 | |
| 0.1.274 | 2 / 3 | |
| 0.1.273 | 2 / 3 | |
| 0.1.272 | 2 / 3 | |
| 0.1.271 | 2 / 3 | |
| 0.1.270 | 2 / 3 | |
| 0.1.269 | 2 / 3 | |
| 0.1.268 | 2 / 3 | |
| 0.1.267 | 2 / 3 | |
| 0.1.266 | 2 / 3 | |
| 0.1.265 | 2 / 3 | |
| 0.1.264 | 2 / 3 | |
| 0.1.263 | 2 / 3 | |
| 0.1.262 | 2 / 3 | |
| 0.1.261 | 2 / 3 | |
| 0.1.260 | 2 / 3 | |
| 0.1.259 | 2 / 3 | |
| 0.1.258 | 2 / 3 | |
| 0.1.257 | 2 / 3 | |
| 0.1.256 | 2 / 3 | |
| 0.1.255 | 2 / 3 | |
| 0.1.254 | 2 / 3 | |
| 0.1.253 | 2 / 3 | |
| 0.1.252 | 2 / 3 | |
| 0.1.251 | 2 / 3 | |
| 0.1.250 | 2 / 3 | |
| 0.1.249 | 2 / 3 | |
| 0.1.248 | 2 / 3 | |
| 0.1.247 | 2 / 3 | |
| 0.1.246 | 2 / 3 | |
| 0.1.245 | 2 / 3 | |
| 0.1.244 | 2 / 3 | |
| 0.1.243 | 2 / 3 | |
| 0.1.242 | 2 / 3 | |
| 0.1.237 | 2 / 3 | |
| 0.1.236 | 2 / 3 | |
| 0.1.235 | 2 / 3 | |
| 0.1.234 | 2 / 3 | |
| 0.1.233 | 2 / 3 | |
| 0.1.232 | 2 / 3 | |
| 0.1.231 | 2 / 3 | |
| 0.1.230 | 2 / 3 | |
| 0.1.229 | 2 / 3 | |
| 0.1.228 | 2 / 3 | |
| 0.1.227 | 2 / 3 | |
| 0.1.226 | 2 / 3 | |
| 0.1.225 | 2 / 3 | |
| 0.1.224 | 2 / 3 | |
| 0.1.223 | 2 / 3 | |
| 0.1.222 | 2 / 3 | |
| 0.1.221 | 2 / 3 | |
| 0.1.220 | 2 / 3 | |
| 0.1.219 | 2 / 3 | |
| 0.1.218 | 2 / 3 | |
| 0.1.217 | 2 / 3 | |
| 0.1.216 | 2 / 3 | |
| 0.1.215 | 2 / 3 | |
| 0.1.213 | 2 / 3 | |
| 0.1.212 | 2 / 3 | |
| 0.1.211 | 2 / 3 | |
| 0.1.210 | 2 / 3 | |
| 0.1.209 | 2 / 3 | |
| 0.1.208 | 2 / 3 | |
| 0.1.207 | 2 / 3 | |
| 0.1.206 | 2 / 3 | |
| 0.1.205 | 2 / 3 | |
| 0.1.204 | 2 / 3 | |
| 0.1.203 | 2 / 3 | |
| 0.1.202 | 2 / 3 | |
| 0.1.201 | 2 / 3 | |
| 0.1.200 | 2 / 3 | |
| 0.1.199 | 2 / 3 | |
| 0.1.198 | 2 / 3 | |
| 0.1.197 | 2 / 3 | |
| 0.1.196 | 2 / 3 |
v0.1.300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.299
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.290
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.289
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.288
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.287
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.286
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.284
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.283
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.277
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.269
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.267
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.265
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.264
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.263
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.262
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.251
2 findingsPackage name '@ottocode/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.