expressjs/csurf
CSRF token middleware observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 21
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4564
- days_rel: n/a
- days_push: 476
- n_releases_24m: 0
Adoption not part of the score
2307 stars · 218 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
csurf is Node.js CSRF protection middleware for Express that creates and validates CSRF tokens via session or cookie-based storage. The repository is archived and no longer actively maintained.
Use cases
- protect express forms from csrf attacks
- add csrf tokens to nodejs web app
- validate csrf token on state-changing requests
- double submit cookie csrf protection
- csrf middleware for express session
When to choose
- you maintain a legacy Express app already using csurf
- you need the classic session-based CSRF token pattern
When to avoid
- starting a new project - the repo is archived and unmaintained
- you need security fixes or ongoing support
- you use a non-Express framework
Facets
library · maturity abandoned
middleware security auth security web-development backend csrf express csrf-protection double-submit-cookie archived nodejs
2 sources
- readme: https://github.com/expressjs/csurf · fetched 2026-08-28 · 70b9f5394335
- registry_npm: https://registry.npmjs.org/csurf · fetched 2026-08-29 · 5facb05d6b04
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| expressjs/csurf | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem