Is @graphiql/plugin-history safe to use?

@graphiql/plugin-history has no known vulnerabilities on the latest version (0.4.2). DepScope rates its health at 87/100 (low risk).

What is the latest version of @graphiql/plugin-history?

The latest version of @graphiql/plugin-history is 0.4.2, released 2026-05-11.

Does @graphiql/plugin-history have known vulnerabilities?

No known vulnerabilities on the latest version of @graphiql/plugin-history.

Is @graphiql/plugin-history deprecated?

No, @graphiql/plugin-history is actively maintained. Latest release: 0.4.2 (2026-05-11).

What are alternatives to @graphiql/plugin-history?

Popular alternatives to @graphiql/plugin-history in npm include: ?, semver, ansi-styles, minimatch, debug.

What license does @graphiql/plugin-history use?

@graphiql/plugin-history is licensed under MIT.

@graphiql/plugin-history

npmv0.4.2

- `useHistory`: Persists executed requests in storage - `useHistoryActions`: Actions related to the history

License MITpermissive122 versions5 maintainers3 deps390,905 weekly dl

graphql/graphiql

/ 100

Health

safe to use

@graphiql/[email protected] is safe to use (health: 87/100)

Health breakdown0 – 100

20/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

13/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

zustand @graphiql/toolkit react-compiler-runtime

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@graphiql/plugin-history