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 #2701

Open
myOmikron opened this issue Nov 24, 2022 · 1 comment
Open

SECURITY #2701

myOmikron opened this issue Nov 24, 2022 · 1 comment

Comments

@myOmikron
Copy link

I couldn't find any information regarding handling of incidents / security problems on this repository. As this is IMHO quite important for a web-framework it would be nice to have some sort of contact information (email + pgp preferred over proprietary chats) and information about how to proceed further, what steps are executed and how quickly responses can be expected.

Some proposals:

  • Add a security policy via github. If a SECURITY.md file is found in the root of the repository, it is included in the About section.
  • Add a section in the README on how to establish contacts regarding security considerations
@WebFreak001
Copy link
Contributor

There hasn't been any response from vibe.d maintainers yet, but if you have something to report, you can probably send a mail to the dlang security team (see https://dlang.org/security.html), they are most likely to get in touch with the vibe.d maintainers and get fixes in.

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

2 participants