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 13
- Secret scanning, 2 of 13
- Push protection, 3 of 13
- Secret security with GitHub, 4 of 13
- About secret scanning alerts, 5 of 13
- Custom patterns, 6 of 13
- Validity checks, 7 of 13
- Delegated bypass for push protection, 8 of 13
- Bypass requests for push protection, 9 of 13
- GitHub secret types, 10 of 13
- Secret scanning push protection metrics, 11 of 13
- Push protection from the command line, 12 of 13
- Working with push protection from the REST API, 13 of 13
- 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 15
- Best practices for maintaining dependencies, 2 of 15
- Dependency graph, 3 of 15
- How the dependency graph recognizes dependencies, 4 of 15
- Dependency review, 5 of 15
- Dependabot alerts, 6 of 15
- Metrics for Dependabot alerts, 7 of 15
- Dependabot security updates, 8 of 15
- Dependabot version updates, 9 of 15
- Dependabot pull requests, 10 of 15
- Multi-ecosystem updates, 11 of 15
- About the dependabot.yml file, 12 of 15
- Dependabot auto-triage rules, 13 of 15
- Dependabot job logs, 14 of 15
- Immutable releases, 15 of 15
- Concepts for vulnerability reporting and management, 4 of 5
- Concepts for security at scale, 5 of 5