Files
starter-workflows/code-scanning
Bishal Prasad dbba84eb87 revert back to "Dependency review" category
The CI test needs to be fixed and not the other way round.
2022-04-01 10:03:32 +05:30
..
2022-03-28 22:40:48 +05:30
2022-02-14 15:19:56 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2021-04-17 14:08:56 -04:00
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30

Code Scanning Workflows

GitHub code scanning is a developer-first, GitHub-native approach to easily find security vulnerabilities before they reach production. Before you can configure code scanning for a repository, you must enable code scanning by adding a GitHub Actions workflow to the repository. For more information, see Setting up code scanning for a repository.