-
Notifications
You must be signed in to change notification settings - Fork 0
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 Policy violation SECURITY.md #2
Comments
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
28 similar comments
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
29 similar comments
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
Updating issue after ping interval. See its status below. Security policy not enabled. To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
This issue was automatically created by Allstar.
Security Policy Violation
Security policy not enabled.
A SECURITY.md file can give users information about what constitutes a vulnerability and how to report one securely so that information about a bug is not publicly visible. Examples of secure reporting methods include using an issue tracker with private issue support, or encrypted email with a published key.
To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/githubfoam/zeek-sandbox/security/policy to enable.
For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository.
This issue will auto resolve when the policy is in compliance.
Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.
The text was updated successfully, but these errors were encountered: