apollo-server-errors 3.2.0

apollo-server-errors@3.2.0 was published on 2021-10-11. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=12.0.

Deprecated: The `apollo-server-errors` package is part of Apollo Server v2 and v3, which are now end-of-life (as of October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the `@apollo/server` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.

All apollo-server-errors versions · Permanent reference to 3.2.0 · Latest release

Package specifications

Version3.2.0
License declarationMIT
Published2021-10-11T20:58:31.453Z
Node.js requirement>=12.0
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size26.64 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars13954
Repository forks2001

Install apollo-server-errors 3.2.0

npm install apollo-server-errors@3.2.0
pnpm add apollo-server-errors@3.2.0
yarn add apollo-server-errors@3.2.0

Runtime dependencies

  • None declared

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.

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

    Evidence and freshness