@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, 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: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 51 of 195)
| Version | Deps | Published |
|---|---|---|
| 0.1.375 | 2 / 3 | |
| 0.1.374 | 2 / 3 | |
| 0.1.373 | 2 / 3 | |
| 0.1.372 | 2 / 3 | |
| 0.1.371 | 2 / 3 | |
| 0.1.370 | 2 / 3 | |
| 0.1.369 | 2 / 3 | |
| 0.1.368 | 2 / 3 | |
| 0.1.367 | 2 / 3 | |
| 0.1.366 | 2 / 3 | |
| 0.1.365 | 2 / 3 | |
| 0.1.364 | 2 / 3 | |
| 0.1.363 | 2 / 3 | |
| 0.1.362 | 2 / 3 | |
| 0.1.361 | 2 / 3 | |
| 0.1.360 | 2 / 3 | |
| 0.1.359 | 2 / 3 | |
| 0.1.358 | 2 / 3 | |
| 0.1.357 | 2 / 3 | |
| 0.1.356 | 2 / 3 | |
| 0.1.355 | 2 / 3 | |
| 0.1.354 | 2 / 3 | |
| 0.1.353 | 2 / 3 | |
| 0.1.352 | 2 / 3 | |
| 0.1.351 | 2 / 3 | |
| 0.1.350 | 2 / 3 | |
| 0.1.349 | 2 / 3 | |
| 0.1.348 | 2 / 3 | |
| 0.1.347 | 2 / 3 | |
| 0.1.346 | 2 / 3 | |
| 0.1.345 | 2 / 3 | |
| 0.1.344 | 2 / 3 | |
| 0.1.343 | 2 / 3 | |
| 0.1.342 | 2 / 3 | |
| 0.1.341 | 2 / 3 | |
| 0.1.340 | 2 / 3 | |
| 0.1.339 | 2 / 3 | |
| 0.1.338 | 2 / 3 | |
| 0.1.337 | 2 / 3 | |
| 0.1.336 | 2 / 3 | |
| 0.1.335 | 2 / 3 | |
| 0.1.334 | 2 / 3 | |
| 0.1.333 | 2 / 3 | |
| 0.1.332 | 2 / 3 | |
| 0.1.331 | 2 / 3 | |
| 0.1.327 | 2 / 3 | |
| 0.1.326 | 2 / 3 | |
| 0.1.325 | 2 / 3 | |
| 0.1.324 | 2 / 3 | |
| 0.1.323 | 2 / 3 | |
| 0.1.322 | 2 / 3 |
v0.1.375
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.374
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.373
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.372
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.371
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.370
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.369
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.368
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.367
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.366
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.365
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.364
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.363
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.362
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.361
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.360
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.359
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.358
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.357
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.356
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.355
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.354
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.353
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.352
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.351
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.350
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.349
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.348
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.347
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.346
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.345
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.344
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.343
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.341
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.340
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.339
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.338
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.337
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.336
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.335
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.334
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.333
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.332
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.