apollo-link-http-common 0.2.8

Http utilities for Apollo Link shared across all links using http

apollo-link-http-common@0.2.8 was published on 2018-12-15. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All apollo-link-http-common versions · Permanent reference to 0.2.8 · Latest release

Package specifications

Version0.2.8
License declarationMIT
Published2018-12-15T01:55:01.009Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size33.00 KiB
Published file count8
Package typeNot declared
ES module entry./lib/index.js
Default entry./lib/bundle.umd.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies8
Repository stars1423
Repository forks334

Install apollo-link-http-common 0.2.8

npm install apollo-link-http-common@0.2.8
pnpm add apollo-link-http-common@0.2.8
yarn add apollo-link-http-common@0.2.8

Runtime dependencies

Peer requirements

  • graphql ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0

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.

Code-Review0/10 — Found 2/27 approved changesets -- score normalized to 0
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness