Skip to content
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

Found a possible security concern #3393

Open
zidingz opened this issue Sep 27, 2021 · 2 comments
Open

Found a possible security concern #3393

zidingz opened this issue Sep 27, 2021 · 2 comments

Comments

@zidingz
Copy link

zidingz commented Sep 27, 2021

Hey there!

I belong to an open source security research community, and a member (@ready-research) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

@MartinKolarik
Copy link
Member

It's true it could be moved to a separate file, but there is a contact here: https://github.com/ractivejs/ractive/blob/dev/CONTRIBUTING.md#reporting-security-vulnerabilities

@evs-chris I'm not sure if you're on that list though. If not and you want to keep using it, let me know and I'll make you the owner.

@evs-chris
Copy link
Contributor

Yeah, I'm not sure if I'm on that list or not, so please add me if I'm not. I think that list will be fine for now, and I'll look at creating a separate security doc in a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants