docs: add a security policy - #13
Merged
Merged
Conversation
There was no SECURITY.md here, so a vulnerability report had nowhere to go except a public issue. Private vulnerability reporting is enabled on the repo now and the file points at the advisory form. No version table and no response-time promise: there are no backport branches to describe, and a stale support matrix is exactly what went wrong with safe-jsx's copy. Repo file only. The files array is untouched, so no published tarball changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added a security policy here, and the same file to the other four publishing repos: safe-jsx, magic, react-native-magic-modal and react-native-code-push-plugin. Only the advisory link differs between them.
It points at GitHub's private advisory form:
https://github.com/GSTJ/react-native-magic-toast/security/advisories/new
I turned private vulnerability reporting on for all five repos.
I left the version support table out. safe-jsx had one written in 2023 that still claimed
1.1.xwas the supported line while the package sat at 1.3.4, and none of these packages keep backport branches. A table here would rot the same way. There's no response-time promise in it either, since that's not something anyone can hold to on a personal OSS project.This one is a repo file only. I didn't touch any
filesarray, andnpm packproduces what it did before.