@taquito/http-utils 17.3.1

*TypeDoc style documentation is available [here](https://tezostaquito.io/typedoc/modules/_taquito_http_utils.html)*

@taquito/http-utils@17.3.1 was published on 2023-09-14. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=16.

All @taquito/http-utils versions · Permanent reference to 17.3.1 · Latest release

Package specifications

Version17.3.1
License declarationApache-2.0
Published2023-09-14T17:53:54.513Z
Node.js requirement>=16
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size239.01 KiB
Published file count23
Package typeNot declared
ES module entrydist/taquito-http-utils.es6.js
Default entrydist/taquito-http-utils.umd.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars322
Repository forks124

Install @taquito/http-utils 17.3.1

npm install @taquito/http-utils@17.3.1
pnpm add @taquito/http-utils@17.3.1
yarn add @taquito/http-utils@17.3.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Code-Review0/10 — Found 0/17 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions7/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices5/10 — badge detected: Passing
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Packaging10/10 — packaging workflow detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST9/10 — SAST tool detected but not run on all commits
Fuzzing0/10 — project is not fuzzed

Evidence and freshness