-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add activity feed API #988
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
const express = require('express'); | ||
const app = express(); | ||
const port = 3000; | ||
|
||
// Fake data for the activity feed | ||
const activityFeed = [ | ||
{ | ||
id: 1000, | ||
title: 'New Photo Uploaded', | ||
body: 'Alice uploaded a new photo to her album.' | ||
}, | ||
{ | ||
id: 2000, | ||
title: 'Comment on Post', | ||
body: "Bob commented on Charlie's post." | ||
}, | ||
{ | ||
id: 13, | ||
title: 'Status Update', | ||
body: 'Charlie updated their status: "Excited about the new project!"' | ||
} | ||
]; | ||
|
||
app.get('/feed', (req, res) => { | ||
res.json(activityFeed); | ||
}); | ||
|
||
app.listen(port, () => { | ||
console.log(`Server running on port ${port}`); | ||
}); |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Semgrep identified an issue in your code:
A CSRF middleware was not detected in your express application. Ensure you are either using one such as
csurf
orcsrf
(see rule references) and/or you are properly doing CSRF validation in your routes with a token or cookies.To resolve this comment:
✨ Commit Assistant fix suggestion
View step-by-step instructions
csurf
middleware by running the command:$ npm install csurf
.csurf
at the top of your file withconst csurf = require('csurf');
.csurf
middleware to your Express app. You can do this by addingapp.use(csurf());
after initializing your Express app withconst app = express();
.csurf
requires either to store the CSRF tokens. If not already included, install and configure one, such asexpress-session
orcookie-parser
./feed
route, you can include the CSRF token in the response by addingres.json({ activityFeed, csrfToken: req.csrfToken() });
.This setup will help protect your application from CSRF attacks by ensuring that requests include a valid CSRF token.
💬 Ignore this finding
Reply with Semgrep commands to ignore this finding.
/fp <comment>
for false positive/ar <comment>
for acceptable risk/other <comment>
for all other reasonsAlternatively, triage in Semgrep AppSec Platform to ignore the finding created by express-check-csurf-middleware-usage.
You can view more details about this finding in the Semgrep AppSec Platform.