Security Policy violation SECURITY.md #17
Comments
|
Updating issue after ping interval. Status: To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/atsign-foundation/private_fit/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
4 similar comments
|
Updating issue after ping interval. Status: To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/atsign-foundation/private_fit/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. Status: To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/atsign-foundation/private_fit/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. Status: To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/atsign-foundation/private_fit/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. Status: To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/atsign-foundation/private_fit/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/atsign-foundation/private_fit/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
3 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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
6 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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/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/atsign-foundation/private_fit/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
1 similar comment
|
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/atsign-foundation/private_fit/security/policy to enable. For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. |
|
Policy is now in compliance. Closing issue. |
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/atsign-foundation/private_fit/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: