graphql-tools 3.0.3

Useful tools to create and manipulate GraphQL schemas.

graphql-tools@3.0.3 was published on 2018-06-25. Its manifest declares 5 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This package has been deprecated and now it only exports makeExecutableSchema. And it will no longer receive updates. We recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc. Check out https://www.graphql-tools.com to learn what package you should use instead

All graphql-tools versions · Permanent reference to 3.0.3 · View npm registry JSON · Latest release

Package specifications

Version3.0.3
License declarationMIT
Published2018-06-25T19:13:00.147Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size341.96 KiB
Published file count125
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies12
Repository stars5432
Repository forks830

Install graphql-tools 3.0.3

npm install graphql-tools@3.0.3
pnpm add graphql-tools@3.0.3
yarn add graphql-tools@3.0.3

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.

Code-Review0/10 — Found 1/11 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness