Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 18:02 UTC

ljharb / qs

A querystring parser and serializer with nesting support

JavaScriptBSD-3-Clause★ 8,942 stars⑂ 893 forkssince Jul 2014View on GitHub ↗

ljharb/qs holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (93/100) and lowest on AI Readiness (28/100). It was last updated 24 days ago. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

86
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).

Ownership

Jordan HarbandPersonal account
8,212 followers283 public repossince Jan 2009@socketdev @tc39

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmqs6.15.3685,318,62614940 days agoquerystringqsqueryurlparsestringify

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

74Good · 21% of overall
How it's scored
28.8/36Push recencylast push 24 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume188 commits in the last year
10/10OpenSSF Scorecard: Maintained21 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year188
human_commit_share1
days_since_last_push24
active_weeks_last_year19
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
36/36Release recencylatest release 40 days ago
19.8/27Release cadencea release every ~64.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv6.15.3
releases_from_tagsyes
days_since_latest_release40
mean_days_between_releases64.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

93Exceptional · 17% of overall
How it's scored
60/60Stars8,942 stars
24.6/25Forks893 forks
10.1/15Watchers66 watchers
Inputs used
forks893
stars8,942
watchers66
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-3-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbestpractices.coreinfrastructure.org
has_pull_request_templateno
How it's scored
80/80Monthly downloads685,318,626 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesqs
dependents
ecosystemsnpm
total_downloads
monthly_downloads685,318,626
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.2/22.5Commit distributiontop contributor authored 64% of commits
13.5/13.5Contributor breadth67 contributors
10/10OpenSSF Scorecard: Contributorsproject has 67 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled67
top_contributor_share0.636
How it's scored
36/42Issue resolution86% of issues closed
19.7/30PR acceptance117/178 decided PRs merged
0/13Newcomer PR acceptance0/5 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/30 approved changesets -- score normalized to 2
Inputs used
merged_prs117
open_issues51
closed_issues309
prs_merged_7d0
prs_decided_7d5
prs_merged_30d0
prs_decided_30d5
issue_closed_ratio0.858
closed_unmerged_prs61
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d5
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach8,212 followers of ljharb
25/25Track record283 public repos, account ~17 yr old
Inputs used
followers8,212
owner_typeUser
is_verified
owner_loginljharb
public_repos283
account_age_days6,415
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 40 days ago
20/20Version history149 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesqs
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
0/10Wiki
Inputs used
topicsjavascript, encoding, querystrings, nodejs, node, browsers, url-parsing, stringify, parse
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practicesbadge detected: Passing
1.5/7.5Code-ReviewFound 7/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 67 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained21 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages21
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:qs@6.15.3 runtime dependency closure — what installing the published package pulls in — 21 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

28At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.1/40Legible commit history17 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.17
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
0/11Static type checking
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
44/55Manageable file sizes2/10 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes80,338
source_files_sampled10
oversized_source_files2

Key facts

8,942GitHub stars
67contributors
188commits, last 12 months
24days since last push
100releases
1bus factor
51open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 893 ⇿
0Stars
893Forks
100Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

02004006008001,000886312014-072020-072026-07
Major 4Minor 18Patch 78

Each point covers 11 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-04 18:01 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
5CII-Best-Practicesbadge detected: Passing
2Code-ReviewFound 7/30 approved changesets -- score normalized to 2
10Contributorsproject has 67 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmes-define-property^1.0.1package.json
npmside-channel^1.1.1package.json
All dependencies 34

Full resolved dependency set from the GitHub dependency graph: 2 direct and 32 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmes-define-property^1.0.1direct
npmside-channel^1.1.1direct
npm@browserify/envify^6.0.0indirect
npm@browserify/uglifyify^6.0.0indirect
npm@ljharb/eslint-config^22.2.3indirect
npmbrowserify^16.5.2indirect
npmbundle-collapser^1.4.0indirect
npmcommon-shakeify~1.0.0indirect
npmeclint^2.8.1indirect
npmes-value-fixtures^1.7.1indirect
npmeslint^10.7.0indirect
npmevalmd^0.0.20indirect
npmfor-each^0.3.5indirect
npmglob10.3.7indirect
npmhas-bigints^1.1.0indirect
npmhas-override-mistake^1.0.1indirect
npmhas-property-descriptors^1.0.2indirect
npmhas-proto^1.2.0indirect
npmhas-symbols^1.1.0indirect
npmiconv-lite^0.5.2indirect
npmin-publish^2.0.1indirect
npmjackspeak2.1.1indirect
npmjiti^0.0.0indirect
npmmkdirp^0.5.5indirect
npmmock-property^1.1.2indirect
npmmodule-deps^6.2.3indirect
npmnpmignore^0.3.5indirect
npmnyc^10.3.2indirect
npmobject-inspect^1.13.4indirect
npmqs-iconv^1.0.4indirect
npmsafe-publish-latest^2.0.0indirect
npmsafer-buffer^2.1.2indirect
npmtape^5.10.2indirect
npmunassertify^3.0.1indirect
Dependency advisories 0

Installing npm:qs@6.15.3 pulls in 21 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.