Gathering detailed insights and metrics for express-http-context
Gathering detailed insights and metrics for express-http-context
Installations
npm install express-http-contextDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS, UMD
Min. Node Version
>=14.8.0
Node Version
22.14.0
NPM Version
10.9.2
Score
99.7
Supply Chain
88.9
Quality
81.8
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
skonves
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
306 Stars
119 Commits
27 Forks
10 Watchers
19 Branches
10 Contributors
Updated on Jul 03, 2025
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
2.0.1
Package Id
express-http-context@2.0.1
Unpacked Size
7.05 kB
Size
2.98 kB
File Count
6
NPM Version
10.9.2
Node Version
22.14.0
Published on
Apr 19, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Express HTTP Context
Get and set request-scoped context anywhere. This package is an unopinionated, zero-dependency, Express-idiomatic implementation of Node AsyncLocalStorage. It's a great place to store user state, claims from a JWT, request/correlation IDs, and any other request-scoped data.
How to use it
Install: npm i express-http-context
Use the context middleware before the first middleware or handler that needs to have access to the context.
1import express from 'express'; 2import * as httpContext from 'express-http-context'; 3 4const app = express(); 5app.use(httpContext.middleware); 6// All code from here on has access to the same context for each request
Set values based on the incoming request:
1// Example authentication middleware 2app.use(async (req, res, next) => { 3 try { 4 // Get user from data on request 5 const bearer = req.get('Authorization'); 6 const user = await userService.getUser(bearer); 7 8 // Add user to the request-scoped context 9 httpContext.set('user', user); 10 11 return next(); 12 } catch (err) { 13 return next(err); 14 } 15});
Get them from code that doesn't have access to the express req object:
1import * as httpContext from 'express-http-context'; 2 3// Somewhere deep in the Todo Service 4async function createTodoItem(title, content) { 5 // Get the user from the request-scoped context 6 const user = httpContext.get('user'); 7 8 await db.insert({ title, content, userId: user.id }); 9}
Legacy versions
- For Node <7:
npm install --save express-http-context@0 - For Node >=8 <12:
npm install --save express-http-context@1
Contributors
- Steve Konves (@skonves)
- Amiram Korach (@amiram)
- Yoni Rabinovitch (@yonirab)
- DontRelaX (@dontrelax)
- William Durand (@willdurand)
- Kristopher Morris (@beeduck)
Interesting in contributing? Take a look at the Contributing Guidlines
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
8 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
packaging workflow detected
Details
- Info: Project packages its releases by way of GitHub Actions.: .github/workflows/publish.yml:24
Reason
0 existing vulnerabilities detected
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/build.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/version.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/skonves/express-http-context/version.yml/master?enable=pin
- Info: 0 out of 7 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 2 out of 2 npmCommand dependencies pinned
Reason
Found 0/6 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/publish.yml:29
- Warn: no topLevel permission defined: .github/workflows/build.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Warn: no topLevel permission defined: .github/workflows/version.yml:1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 30 are checked with a SAST tool
Score
4.9
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More