Concepts for security and code quality
Learn core concepts for GitHub's security and code quality features.
- Concepts for secret security, 1 of 5
- Secret leakage risks, 1 of 12
- Secret scanning, 2 of 12
- Push protection, 3 of 12
- Secret security with GitHub, 4 of 12
- About secret scanning alerts, 5 of 12
- Custom patterns, 6 of 12
- Delegated bypass for push protection, 7 of 12
- Bypass requests for push protection, 8 of 12
- GitHub secret types, 9 of 12
- Secret scanning push protection metrics, 10 of 12
- Push protection from the command line, 11 of 12
- Working with push protection from the REST API, 12 of 12
- Concepts for code scanning, 2 of 5
- Code scanning, 1 of 9
- Code scanning alerts, 2 of 9
- About setup types for code scanning, 3 of 9
- Integration with code scanning, 4 of 9
- About SARIF files for code scanning, 5 of 9
- Code scanning merge protection, 6 of 9
- Concepts for CodeQL, 7 of 9
- About the tool status page, 8 of 9
- CodeQL pull request alert metrics, 9 of 9
- Supply chain security, 3 of 5
- Supply chain security, 1 of 13
- Best practices for maintaining dependencies, 2 of 13
- Dependency graph, 3 of 13
- How the dependency graph recognizes dependencies, 4 of 13
- Dependency review, 5 of 13
- Dependabot alerts, 6 of 13
- Dependabot security updates, 7 of 13
- Dependabot version updates, 8 of 13
- Dependabot pull requests, 9 of 13
- Multi-ecosystem updates, 10 of 13
- About the dependabot.yml file, 11 of 13
- Dependabot auto-triage rules, 12 of 13
- Dependabot job logs, 13 of 13
- Concepts for vulnerability reporting and management, 4 of 5
- Concepts for security at scale, 5 of 5