Please enable Private Vulnerability Reporting (security disclosure channel)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- security
Research direction
Read the repository's security policy and the linked GitHub documentation on configuring vulnerability reporting for a repository. Check the repository's security settings and enable Private Vulnerability Reporting; done means maintainers can receive reports through GitHub's private reporting channel.
Written by the indexing model from the issue text.
Description
Hi maintainers,
I'm a security researcher and have potential security findings that I'd like to
report privately.
I couldn't find a documented private contact in the repository's security policy or
other project metadata, and this repository does not currently have GitHub Private
Vulnerability Reporting enabled.
Could you please enable Private Vulnerability Reporting for this repository? It is a
free, built-in GitHub feature that gives maintainers a private channel to receive and
triage security reports:
Once it is enabled, I'll submit the technical details, reproduction steps, and
suggested fixes through that private channel. If you prefer another private contact,
please let me know and I'll use that instead.
I'm intentionally not including any vulnerability details in this public issue.
Thanks!
zx — GitHub: @manus-pi
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 712
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 381
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 craftcms/cms
-
bug repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
craftcms/cms#20205 · 1 comment ·
Maintainers usually reply within 1 day
-
bug repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
craftcms/cms#20203 · 1 comment ·
Maintainers usually reply within 1 day
-
[5.x]: Moving an asset with “Replace it” throws TypeError: volumeUid must be of type string, null givenPossibly taken @i-just claimed this 8 days ago. Openbug repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
craftcms/cms#20128 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
bug repo:cms
Difficulty 4/5 3-5 days Newbie friendliness 48/100
craftcms/cms#20386 · 1 comment ·
Maintainers usually reply within 1 day
-
bug repo:cms
Difficulty 3/5 1-2 days Newbie friendliness 63/100
craftcms/cms#20382 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Icinga/icingaweb2-module-director#3188 ·
Maintainers usually reply within 4 days
-
bug ui
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
hashtopolis/server#2614 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 1/5 Under an hour Newbie friendliness 62/100