Merged
Conversation
Member
|
Done. Also enabled |
Member
|
Fixed the link. I think you wanted it to point to https://github.com/lycheeverse/lychee-action/security/advisories/new. (The |
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
2 participants
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.
Hi! I've found a security problem in the action and I want to send a patch, but that would make the patch public and possible attackers could compromise repositories that are using lychee-action.
So to start with the process, I'm opening this to create a SECURITY.md document that will enable
Security policyin the repositorySecuritytab.To send the patch in a private fork, that will not be public, I need that someone with write access to the settings enable
Private vulnerability reporting. The otherSecurity advisoriescan be enabled also without publishing all reports as each report can be marked as public or not later.Note that there is another approach that maybe you want to take. You can create a unique global SECURITY.md file that will apply for each repository on your organization by creating a lycheeverse/.github repository and putting the SECURITY.md file there.