{"full_name":"expressjs/express","owner":"expressjs","name":"express","url":"https://github.com/expressjs/express","description":"Fast, unopinionated, minimalist web framework for node.","homepage":"https://expressjs.com","topics":[],"language":"JavaScript","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/5658226?v=4","created_at":"2009-06-26T18:56:01Z","pushed_at":"2026-11-02T20:15:26Z","metrics":{"stars":69573,"forks":25397,"watchers":1697,"issues":4088,"prs":2743,"releases":166,"issues_open":null,"issues_closed":null,"prs_open":null,"prs_closed":null,"prs_merged":null,"discussions":206},"growth":{"day":{"stars":0,"forks":7,"base_day":"2026-11-09"}},"history":{"dates":["2026-11-09","2026-11-10"],"stars":[69573,69573],"forks":[25390,25397],"watchers":[1697,1697],"issues_open":[null,null],"prs_open":[null,null]},"boards":{},"same_owner":[],"issues":[{"number":2818,"title":"include \"typings\" field in package.json","comments":34,"created_at":"2015-11-30T17:08:56Z"},{"number":2151,"title":"Params registered on app available in routers used by app","comments":34,"created_at":"2014-05-29T19:05:59Z"},{"number":2281,"title":"'/' route breaks strict routing","comments":33,"created_at":"2014-08-05T16:16:46Z"},{"number":1980,"title":"Please add app.route('foo').use()","comments":31,"created_at":"2014-03-16T05:35:56Z"},{"number":2501,"title":"Add originalRoute like originalUrl","comments":30,"created_at":"2015-01-16T11:37:13Z"},{"number":6711,"title":"Restore Support for app.all('*') Wildcard in Express v5","comments":23,"created_at":"2025-08-17T12:45:43Z"},{"number":2896,"title":"Define error-handling middleware functions explicitly (without arity detection)","comments":23,"created_at":"2016-02-19T08:10:12Z"},{"number":3367,"title":"Suggestion: Implicitly-named error handler","comments":22,"created_at":"2017-07-17T10:06:02Z"}],"discussions":[{"number":7579,"title":"Two different 429s from one Express middleware, and how a client should tell them apart","comments":0,"category":"Show and tell","created_at":"2026-11-01T14:45:06Z"},{"number":7570,"title":"Two Express monitoring gotchas: load order and where the error handler goes","comments":0,"category":"Show and tell","created_at":"2026-10-28T08:59:43Z"},{"number":7524,"title":"If `process.env.NODE_ENV` is not explicitly set, it returns `undefined` instead of `development`","comments":2,"category":"Q&A","created_at":"2026-10-16T16:29:31Z"},{"number":7505,"title":"Express 5.2.1 loading results on Node.js, Bun and Deno","comments":1,"category":"Show and tell","created_at":"2026-10-05T12:18:09Z"},{"number":7492,"title":"React Frontend with Express: Server-Side Rendering or API-Based Architecture?","comments":1,"category":"Q&A","created_at":"2026-09-28T16:22:58Z"},{"number":7413,"title":"One-line idempotency middleware for Express","comments":1,"category":"Show and tell","created_at":"2026-08-09T15:53:18Z"},{"number":7359,"title":"Express 5 + async/await: How to handle unhandled promise rejections without crashing?","comments":5,"category":"Q&A","created_at":"2026-07-04T11:10:33Z"},{"number":7312,"title":"Interpreting ownership and activity patterns in lib/","comments":0,"category":"General","created_at":"2026-06-12T05:14:26Z"}],"latest_release":{"name":"v5.3.0","tag":"v5.3.0","published_at":"2026-10-09T12:50:31Z","body":"## Highlights\r\n\r\n### 🐞 Bug fixes\r\n\r\n- Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by [@YuryShkoda](https://github.com/YuryShkoda) in [#4893](https://github.com/expressjs/express/pull/4893)\r\n\r\n\r\n    Fixed the behavior of `res.send()` to prevent conflicts between `Content-Length` and `Transfer-Encoding` HTTP headers in responses. The `Content-Length` header in `res.send()` is now only added when a `Transfer-Encoding` header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a `Transfer-Encoding` header - by [@cuishuang](https://github.com/cuishuang) in [#7459](https://github.com/expressjs/express/pull/7459)\r\n\r\n* Upgrade `qs` to `^6.16.0`, which fixes [CVE-2026-2391](https://www.cve.org/CVERecord?id=CVE-2026-2391) ([GHSA-w7fw-mjwx-w883](https://github.com/ljharb/qs/security/advisories/GHSA-w7fw-mjwx-w883)), [CVE-2026-82417](https://www.cve.org/CVERecord?id=CVE-2026-82417) ([GHSA-4mjr-xmp4-gh2g](https://github.com/advisories/GHSA-4mjr-xmp4-gh2g)) and [CVE-2026-82562](https://www.cve.org/CVERecord?id=CVE-2026-82562) ([GHSA-x5fp-wj9c-mxmx](https://github.com/advisories/GHSA-x5fp-wj9c-mxmx)): `arrayLimit` bypasses in comma parsing and a denial of service via an attacker-controlled `isBuffer` - by [@davetashner](https://github.com/davetashner) in [#7057](https://github.com/expressjs/express/pull/7057) and [#7478](https://github.com/expressjs/express/pull/7478), and [@cyphercodes](https://github.com/cyphercodes) in [#7305](https://github.com/expressjs/express/pull/7305)\r\n\r\n* Upgrade `proxy-addr` to `^2.0.8`, which fixes [CVE-2026-90711](https://www.cve.org/CVERecord?id=CVE-2026-90711) - by [@lazerg](https://github.com/lazerg) in [#7474](https://github.com/expressjs/express/pull/7474)\r\n\r\n### 🚀 Improvements\r\n\r\n* Allow conditional revalidation for QUERY requests. `req.fresh` previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by [@Cherry](https://github.com/Cherry) in [#7366](https://github.com/expressjs/express/pull/7366)\r\n\r\n    ```js\r\n    // QUERY /reports with If-None-Match: \"12345\"\r\n    app.query('/reports', (req, res) => {\r\n      res.set('ETag', '\"12345\"');\r\n      res.send(results); // now responds 304 Not Modified\r\n    });\r\n    ```\r\n\r\n* Improve HTML structure in `res.redirect()` responses when HTML format is accepted by adding `<!DOCTYPE html>`, `<title>`, and `<body>` tags for better browser compatibility - by [@Bernice55231](https://github.com/Bernice55231) in [#5167](https://github.com/expressjs/express/pull/5167)\r\n\r\n* When calling `app.render` with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by [AkaHarshit](https://github.com/AkaHarshit) in [#6903](https://github.com/expressjs/express/pull/6903)\r\n\r\n    ```js\r\n    app.render('index', null, callback); // now works as expected\r\n    ```\r\n\r\n* Upgrade `content-type` to `^2.0.0`, bringing a faster parser (~1.5x quicker `Content-Type` parsing/formatting in `res.send()`) along with a behavior change: `res.send()` now keeps any existing parameters when adding the charset and no longer throws on a `Content-Type` that fails to parse. `type-is` is upgraded to `^2.1.0` as part of the same change - by [@blakeembrey](https://github.com/blakeembrey) in [#7234](https://github.com/expressjs/express/pull/7234)\r\n\r\n    ```js\r\n    res.set('Content-Type', 'text/plain; foo=bar').send('hey');\r\n    // -> Content-Type: text/plain; foo=bar; charset=utf-8\r\n    ```\r\n\r\n* The default error handler now logs the full error object instead of only its stack trace, so nested details such as `Error.cause` and "},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-10T09:35:25Z","history_start":"2026-09-06"}