{"meta":{"title":"Fixing reported vulnerabilities","intro":"Build skills in collaborating on fixing security vulnerabilities in repositories.","product":"Security and code quality","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/code-security","title":"Security and code quality"},{"href":"/en/enterprise-cloud@latest/code-security/tutorials","title":"Tutorials"},{"href":"/en/enterprise-cloud@latest/code-security/tutorials/fix-reported-vulnerabilities","title":"Fix reported vulnerabilities"}],"documentType":"subcategory"},"body":"# Fixing reported vulnerabilities\n\nBuild skills in collaborating on fixing security vulnerabilities in repositories.\n\n## Links\n\n* [Collaborating in a temporary private fork to resolve a repository security vulnerability](/en/enterprise-cloud@latest/code-security/tutorials/fix-reported-vulnerabilities/collaborate-in-a-fork)\n\n  You can create a temporary private fork to privately collaborate on fixing a security vulnerability in your public repository.\n\n* [Best practices for writing repository security advisories](/en/enterprise-cloud@latest/code-security/tutorials/fix-reported-vulnerabilities/write-security-advisories)\n\n  When you create or edit security advisories, the information you provide is easier for other users to understand when you specify the ecosystem, package name, and affected versions using the standard formats."}