Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 11:37 UTC

expressjs / compression

Node.js compression middleware

JavaScriptMIT★ 2,806 stars⑂ 255 forkssince Jan 2014View on GitHub ↗

expressjs/compression holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (91/100) and lowest on AI Readiness (32/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

87
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.

87
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 73 is calibrated to 87 on the published index scale (record calibration 2026-08-02).

Ownership

expressjsOrganization
2,591 followers50 public repossince Oct 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmcompression1.8.2155,395,487405 days agocompressiongzipdeflatemiddlewareexpressbrotlihttpstream

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
4.8/36Commit cadence — 7/52 weeks with commits
12.1/18Commit volume — 21 commits in the last year
10/10OpenSSF Scorecard: Maintained — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year21
human_commit_share—
days_since_last_push5
active_weeks_last_year7
How it's scored
27/27Ships releases — 32 releases published
36/36Release recency — latest release 5 days ago
5.4/27Release cadence — a release every ~419.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count32
latest_release_tagv1.8.2
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases419.3
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?

91Excellent · 17% of overall
How it's scored
55.9/60Stars — 2,806 stars
20/25Forks — 255 forks
9.5/15Watchers — 53 watchers
Inputs used
forks255
stars2,806
watchers53
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 155,395,487 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescompression
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads155,395,487
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?

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 28 contributors
10/10OpenSSF Scorecard: Contributors — project has 32 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled28
top_contributor_share0.862
How it's scored
38.9/42Issue resolution — 92% of issues closed
17.1/30PR acceptance — 69/121 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 10/12 approved changesets -- score normalized to 8
Inputs used
merged_prs69
open_issues11
closed_issues136
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.925
closed_unmerged_prs52
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
24.5/25Owner reach — 2,591 followers of expressjs
24.4/25Track record — 50 public repos, account ~12 yr old
Inputs used
followers2,591
owner_typeOrganization
is_verifiedno
owner_loginexpressjs
public_repos50
account_age_days4,723

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 5 days ago
20/20Version history — 40 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescompression
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 23 out of 29 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
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/10Topics — 7 topics
0/10Wiki
Inputs used
topicscompression, deflate, expressjs, gzip, javascript, middleware, nodejs
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?

83Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1.8/2.5CI-Tests — 23 out of 29 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 10/12 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 32 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages10
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:compression@1.8.2 runtime dependency closure — what installing the published package pulls in — 10 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes36,799
source_files_sampled2
oversized_source_files0

Key facts

2,806GitHub stars
28contributors
21commits, last 12 months
5days since last push
32releases
1bus factor
11open issues
npmpackage ecosystems

Data collection warnings

  • GraphQL snapshot failed, fell back to REST: GitHub GraphQL error: Something went wrong while executing your query on 2026-09-16T11:36:28Z. Please include `9A10:21CC9F:A177C15:9D4A636:6AAA7F3B` when reporting this issue.
  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 255 ⇿
0Stars
255Forks
31Releases

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.

0408012016020024020262014-012020-052026-09
Major 0Minor 8Patch 23

Each point covers 12 days.

OpenSSF Scorecard 7.9 / 10
7.9aggregate

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-09-16 11:36 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests23 out of 29 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 10/12 approved changesets -- score normalized to 8
10Contributorsproject has 32 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npmbytes3.1.2package.json
npmcompressible~2.0.18package.json
npmdebug2.6.9package.json
npmdestroy1.2.0package.json
npmnegotiator~0.6.4package.json
npmon-headers~1.1.0package.json
npmsafe-buffer5.2.1package.json
npmvary~1.1.2package.json
All dependencies 19

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

RegistryPackageVersionRelation
npmbytes3.1.2direct
npmcompressible~2.0.18direct
npmdebug2.6.9direct
npmdestroy1.2.0direct
npmnegotiator~0.6.4direct
npmon-headers~1.1.0direct
npmsafe-buffer5.2.1direct
npmvary~1.1.2direct
npmafter0.8.2indirect
npmeslint7.32.0indirect
npmeslint-config-standard14.1.1indirect
npmeslint-plugin-import2.32.0indirect
npmeslint-plugin-markdown2.2.1indirect
npmeslint-plugin-node11.1.0indirect
npmeslint-plugin-promise5.2.0indirect
npmeslint-plugin-standard4.1.0indirect
npmmocha9.2.2indirect
npmnyc15.1.0indirect
npmsupertest6.3.4indirect
Dependency advisories 0

Installing npm:compression@1.8.2 pulls in 10 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.