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

Add a security policy (SECURITY.md) for this repo #13

Open
CAM-Gerlach opened this issue Sep 9, 2021 · 3 comments
Open

Add a security policy (SECURITY.md) for this repo #13

CAM-Gerlach opened this issue Sep 9, 2021 · 3 comments
Assignees

Comments

@CAM-Gerlach
Copy link
Collaborator

CAM-Gerlach commented Sep 9, 2021

Adding a security policy might be a good idea given the code both consumes and exposes web-facing data, and GitHub makes it easy to do. @goneall , if SPDX already has something of this sort, that would be preferable; otherwise I can draft something based on the standard template and go ahead with a PR so you can review it.

@goneall
Copy link
Member

goneall commented Sep 9, 2021

@CAM-Gerlach - Sounds like a good idea - please go ahead and create a PR

@CAM-Gerlach
Copy link
Collaborator Author

@goneall So I looked at it in more detail, and most of what we'd say there (who to contact, when to expect updates, if anything is offered in return, etc) would be something for the primary maintainer (you) and the SPDX org to decide, so not sure how much I'm actually qualified to draft after all, sorry, as opposed to you. Its pretty simple and the supported versions table needn't be included, only that the latest API content and the master branch is the only supported version for now; here is a simple example from one of my projects.

We might also want to wait on this for #10 to get resolved; not much point to do this if the API isn't going to be supported long-term or hosted under another org with different policies.

@goneall
Copy link
Member

goneall commented Sep 9, 2021

@CAM-Gerlach I'll look into it after #10 is resolve per suggestion.

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