@graphiql/plugin-history 0.4.1-canary-013fcd87.0

## API

@graphiql/plugin-history@0.4.1-canary-013fcd87.0 was published on 2025-07-18. Its manifest declares 2 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @graphiql/plugin-history versions · Permanent reference to 0.4.1-canary-013fcd87.0 · Latest release

Package specifications

Version0.4.1-canary-013fcd87.0
License declarationMIT
Published2025-07-18T13:03:44.881Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count4
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size45.38 KiB
Published file count15
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies4
Repository stars16927
Repository forks1861

Install @graphiql/plugin-history 0.4.1-canary-013fcd87.0

npm install @graphiql/plugin-history@0.4.1-canary-013fcd87.0
pnpm add @graphiql/plugin-history@0.4.1-canary-013fcd87.0
yarn add @graphiql/plugin-history@0.4.1-canary-013fcd87.0

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-Review5/10 — Found 2/4 approved changesets -- score normalized to 5
Security-Policy4/10 — security policy file detected
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices2/10 — badge detected: InProgress
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness