---
title: "querystringify security advisories"
description: "1 known security advisory for querystringify, with the versions they affect and the version that fixes each."
url: https://inlinr.com/packages/querystringify/security
lang: en
---

[Packages](https://inlinr.com/packages)

# querystringify

2.2.0 · 17 Aug 2020 MIT 50.3M / week [Repository](https://github.com/unshiftio/querystringify) [npm](https://www.npmjs.com/package/querystringify) [Atom feed](https://inlinr.com/packages/feed/querystringify)

Your version 

## Security advisories

From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.

| Line | Newest | Where it stands                                                           |
| ---- | ------ | ------------------------------------------------------------------------- |
|      | 2.2.0  | No known advisory                                                         |
|      | 1.0.0  | 2 open advisories, worst high  · last release Mar 2017, no longer updated |

- High  
[Prototype Pollution in querystringify](https://inlinr.com/advisories/GHSA-hxcm-v35h-mg2x)GHSA-hxcm-v35h-mg2x · 7 Jun 2019

### Quality and security signals

What [npm](https://www.npmjs.com/package/querystringify) and [deps.dev](https://deps.dev/npm/querystringify) say about the latest release. Signals, not a verdict.

Reading npm and deps.dev…

Registry facts last checked 22 Nov 2026\. Releases and advisories last read 22 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
