@apollographql/graphql-upload-8-fork

Fork of graphql-upload@8 that works with graphql@15 for compatibility with apollo-server@2

@apollographql/graphql-upload-8-fork@8.1.4 was published on 2022-10-20. Its manifest declares 7 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.5.

All @apollographql/graphql-upload-8-fork versions · Permanent reference to 8.1.4

Package specifications

Version8.1.4
License declarationMIT
Published2022-10-20T17:39:24.118Z
Node.js requirement>=8.5
Type declarationsBundled declarations
Runtime dependency count7
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size27.85 KiB
Published file count20
Package typeNot declared
ES module entryNot declared
Default entrylib
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies30
Repository stars0
Repository forks6

Install @apollographql/graphql-upload-8-fork 8.1.4

npm install @apollographql/graphql-upload-8-fork@8.1.4
pnpm add @apollographql/graphql-upload-8-fork@8.1.4
yarn add @apollographql/graphql-upload-8-fork@8.1.4

Runtime dependencies

Peer requirements

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.

Maintained0/10 — project is archived
Code-Review0/10 — Found 1/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness