Add SECURITY.md for responsible vulnerability disclosure 🔒
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- markdown
- Domain
- security
Research direction
Create the new SECURITY.md file in the repository root using the policy details in the issue: supported versions and the vulnerability reporting email, instructions, and response time. No code or tests are needed; done means the file clearly documents how to report vulnerabilities privately.
Written by the indexing model from the issue text.
Description
Add SECURITY.md for responsible vulnerability disclosure 🔒
File: SECURITY.md (new file)
No way for security researchers to
report vulnerabilities responsibly 💀 fr!!
Fix: create SECURITY.md in root:
Security Policy 🔒
Supported Versions
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
Reporting a Vulnerability
Please DO NOT open a public GitHub issue
for security vulnerabilities!
Instead email: [email protected]
Include:
- Description of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (optional)
We'll respond within 48 hours and
credit you in the fix! 🙏
No code needed — pure markdown!!
Makes repo look super professional 🔥
GitHub shows a special "Security" tab!! ✨
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 105
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 29
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anoopcodehack/DevBoard
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anoopcodehack/DevBoard#588 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anoopcodehack/DevBoard#587 ·
Maintainers usually reply within 1 day
-
Add bulk delete for selected tasks 🗑️Possibly taken @Mario-Mohar claimed this today. Opengood first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
anoopcodehack/DevBoard#586 · 1 comment ·
Maintainers usually reply within 1 day
-
Add database indexes to Task and User models ⚡Possibly taken @Mario-Mohar claimed this today. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anoopcodehack/DevBoard#584 · 1 comment ·
Maintainers usually reply within 1 day
-
Show blocked tasks count in column header 🚫Possibly taken @anushreemehta6 claimed this 1 day ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
anoopcodehack/DevBoard#583 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in anoopcodehack/DevBoard
Similar issues
-
agent/scanner bug hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rescript-lang/rescript#8765 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4417 ·
Maintainers usually reply within 1 day
-
[Good First Issue]: Add unit tests for NetworkVersionInfoPossibly taken A pull request linked to this issue is open or already merged. OpenGood First Issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hiero-ledger/hiero-sdk-js#4489 ·
Maintainers usually reply within 1 day
-
Add: RiC FeedOpencheck:passed feeds:add
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 9 days