oss-slu / oss-slu/DigitalBoneBox

Protect against DoS attacks

Open
#223 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

back-end enhancement security
Dominant language
JavaScript
Stars
8
Forks
18
Avg merge
8h 17m
Merged PRs (30d)
4

Description

Feature description

A clear and concise description of the feature, and why it should be added to the project.

We want our API to use a cache for temporarily storing all GitHub server data. This is because if we make too many requests, GitHub may limit requests, rendering our application useless. This would open our app up to DoS (Denial of Service) attacks, and we want to prevent this.

EDIT: We are now moving our data to be stored on the server directly. This means caching will not be necessary.


✅ Tasks to be Completed

A checklist of individual tasks that likely must be done before the feature can be considered "complete".

See the attached sub-issues.


Acceptance Criteria

A checklist of conditions that must be met for this task to be considered complete. How will we verify that it's done correctly?

  • All fetching of data is routed through the internal server.
  • All data being fetched by the server is served from files local to the server.

Additional context

Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the attached sub-issues and trace how the application currently fetches GitHub data through its API. Route every fetch through the internal server and verify that the server serves the data from local files, using the acceptance criteria as the completion check.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
api, backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.