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 security policy #259

Merged
merged 1 commit into from
Oct 14, 2024
Merged

Add security policy #259

merged 1 commit into from
Oct 14, 2024

Conversation

mondeja
Copy link
Contributor

@mondeja mondeja commented Oct 13, 2024

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 policy in the repository Security tab.

image

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 other Security advisories can 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.

@mre mre merged commit 762333c into lycheeverse:master Oct 14, 2024
1 of 3 checks passed
@mre
Copy link
Member

mre commented Oct 14, 2024

Done. Also enabled Private vulnerability reporting.

@mre
Copy link
Member

mre commented Oct 14, 2024

Fixed the link. I think you wanted it to point to https://github.com/lycheeverse/lychee-action/security/advisories/new. (The security/ was missing.)

@mondeja mondeja deleted the security-policy branch October 14, 2024 01:55
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

Successfully merging this pull request may close these issues.

2 participants