Note: Since this post was published, we have combined the dependency scanning tool with our LiveDoc service.
Overview
The Developer Portal includes a tool called the dependency scanning tool, which allows users to scan source repositories (currently only GitHub is supported) for any references to assemblies that may be deprecated or targeted for removal by a software team.
Usage
- Setup
- Obtain an API key from the Developer Portal..
- Configure Postman with the base URL for the dependency scanning API.
- Configure input parameters
- Admin users can define the configuration/parameters for scanning a repository in the Admin > Dependency scanning section. Here, we can specify details like:
- Name of the source repository
- URL of the repository
- Output report format
- Name and version of deprecated packages to be scanned
- These configurations are stored in CosmosDB and can be accessed using a unique repository key.
- Admin users can define the configuration/parameters for scanning a repository in the Admin > Dependency scanning section. Here, we can specify details like:
- API call
- Send a
GETrequest to initiate the scan, including both the repository key and API key in the request headers. 
- Send a
- Scan report
- The scan results are saved to Azure blob storage, with the location specified in the response to the scan response.
