sindresorhus/query-string

Parse and stringify URL query strings

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 9th, 2026
Created on November 13th, 2013
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 455
Total Stargazers: 6,906 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.5 days
Mean response time: 183.6 days
90th percentile: 517.1 days
Tracked items: 42

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 3 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (5)
  • enhancement (3)
  • bug (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

query-string is a npm package that parses and stringifies URL query strings.

The package solves the problem of converting between query string formats and JavaScript objects. It handles parsing by accepting a query string with optional leading `?` or `#` characters and returning an object created with `Object.create(null)`. For stringification, it reverses the process. The tool supports multiple array format representations including bracket notation, index notation, comma-separated values, and custom separators. It offers options for decoding URI components, sorting keys, and parsing values as specific types like numbers or booleans through an explicit types schema.

Developers should consider this package for applications requiring flexible query string handling beyond what the native `URLSearchParams` API provides. The README recommends using `URLSearchParams` for simple cases, making query-string most suitable when you need advanced array formatting options, custom type parsing, or precise control over encoding and sorting behavior. The types schema feature is particularly valuable when query parameters might be ambiguous in type, such as phone numbers or IDs that look numeric but should remain strings.

The project maintains active engagement with its codebase through regular updates and responsiveness to issues. Development shows consistent attention to edge cases and user-reported problems, with fixes and enhancements applied steadily. The maintainer demonstrates a commitment to backward compatibility while incrementally improving the API surface, as evidenced by thoughtful additions like the types option for explicit type declarations.