fix: requirements.txt to reduce vulnerabilities #8

	# A sample workflow which checks out the code, builds a container
	# image using Docker and scans that image for vulnerabilities using
	# Snyk. The results are then uploaded to GitHub Security Code Scanning
	#
	# For more examples, including how to limit scans to only high-severity
	# issues, monitor images for newly disclosed vulnerabilities in Snyk and
	# fail PR checks for new vulnerabilities, see https://github.com/snyk/actions/

	name: Snyk Container
	on: push
	jobs:
	snyk:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@master
	- name: Build a Docker image
	run: docker build -t mpast/mobile_audit:latest .
	- name: Run Snyk to check Docker image for vulnerabilities
	# Snyk can be used to break the build when it detects vulnerabilities.
	# In this case we want to upload the issues to GitHub Code Scanning
	continue-on-error: true
	uses: snyk/actions/docker@master
	env:
	# In order to use the Snyk Action you will need to have a Snyk API token.
	# More details in https://github.com/snyk/actions#getting-your-snyk-token
	# or you can signup for free at https://snyk.io/login
	SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
	with:
	image: mpast/mobile_audit:latest
	args: --file=Dockerfile
	- name: Upload result to GitHub Code Scanning
	uses: github/codeql-action/upload-sarif@v2
	with:
	sarif_file: snyk.sarif

Provide feedback