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

Security reporting procedure #403

Open
davewasmer opened this issue Oct 11, 2017 · 2 comments
Open

Security reporting procedure #403

davewasmer opened this issue Oct 11, 2017 · 2 comments

Comments

@davewasmer
Copy link
Collaborator

No description provided.

@seawatts
Copy link
Contributor

Can you provide more detail here?

@davewasmer
Copy link
Collaborator Author

We should have a written, publicly available process for responsibly reporting security flaws in the framework. Something that documents how to privately report such issues, timeliness for communication, etc. This is standard procedure for mature frameworks, and beyond the intrinsic value of the procedure, is a signal of the seriousness of the project.

For example: https://emberjs.com/security/

@davewasmer davewasmer added this to the v0.1.0-beta.1 milestone Oct 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants