csurf
CSRF token middleware (by expressjs)
cookie-session
Simple cookie-based session middleware (by expressjs)
Our great sponsors
| csurf | cookie-session | |
|---|---|---|
| 5 | 3 | |
| 2,294 | 1,105 | |
| - | 0.5% | |
| 4.7 | 7.2 | |
| over 1 year ago | 3 months ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
csurf
Posts with mentions or reviews of csurf.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-19.
-
NodeJS Security Best Practices
To learn more about CSRF. Go here Consider using csurf
-
Help me module export
Additionally, I don't mean to offend you, but I doubt your bot will be "secure" if you don't have the appropriate knowledge and experience of secure programming practices. For example, consider this piece of code from the popular (now deprecated) csurf:
-
can we implement custom csrf like let take an example I am using next js and express for api and I want to implement a custom csrf token generator and validator like jwt we can generate and validate. so we donreq the api for csrf token we generate our own with some kind of secret then validate that.
it's looking like express/csurf is archived and deprecated (as of 5 hours ago)... ref
-
Understanding CSRF Attacks
If you use Express, I recommend using the csurf library since it's more robust and flexible compared to what I could show in this example above.
-
CSRF Protection in Next.js
We will use a popular npm package to handle CSRF called csurf.
cookie-session
Posts with mentions or reviews of cookie-session.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-25.
-
Stop using JSON Web Tokens for user sessions
The lack of logout and XSS are problems, but I ran into a couple apps that completely forgot to expire sessions due to lacking framework support. In nodejs's cookie-session and @google-cloud/connect-firestore sessions never expire. This issue impacts downstream software including, awkwardly enough, Google's Passkey demo apps. There isn't interest in fixing this.
Make sure your app is actually using a JWT framework, not a lesser version, and implements basic security practices.
[1] https://github.com/expressjs/cookie-session
[2] https://github.com/googleapis/nodejs-firestore-session
-
Node Authentication Questions
Side note: a JWT in an HttpOnly cookie, which is what some people advocate, is still a cookie-based session. Using a library like cookie-session would already give you the ability to have a signature-verified JSON payload, just like using a JWT would.
-
JWT should not be your default for sessions
Frameworks usually sign cookies by default, or at least offer an option to do so. Some (like Ruby on Rails) can encrypt them for you too. There's nothing really stopping you from storing data in them just like you would a JWT. In fact, frameworks and session libraries often use this cookie storage by default (even in the Node ecosystem, e.g: koa-session, express cookie-session), since an in-memory store can grow to an arbitrary size. Of course, you can also just store a JWT in a cookie, which has the advantage of being standardized in terms of claims and signing algorithms etc.
What are some alternatives?
When comparing csurf and cookie-session you can also consider the following projects:
csrf - Logic behind CSRF token creation and verification.
vue-cookies - A simple Vue.js plugin for handling browser cookies
Next.js - The React Framework
body-parser - Node.js body parsing middleware
express-csrf-double-submit-cookie - Express CSRF token middleware with "Double cookie submit"
session - Simple session middleware for Express
cors - Node.js CORS middleware
cookie-parser - Parse HTTP request cookies
a12n-server - An open source lightweight OAuth2 server
session - Simple session middleware for koa