2 django vulnerabilities found in Pipfile.lock
Remediation
Upgrade django to version 2.0.8 or later. For example:

[packages]

django = ">=2.0.8"
or…
[dev-packages]

django = ">=2.0.8"
Always verify the validity and compatibility of suggestions with your codebase.

Details
CVE-2018-14574 More information
moderate severity
Vulnerable versions: >= 2.0, < 2.0.8
Patched version: 2.0.8
django.middleware.common.CommonMiddleware in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect.

CVE-2018-6188 More information
moderate severity
Vulnerable versions: >= 2.0.0, < 2.0.2
Patched version: 2.0.2
django.contrib.auth.forms.AuthenticationForm in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the confirm_login_allowed() method, as demonstrated by discovering whether a user account is inactive.

2018-12-01T14:44:37.772872+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T14:44:37.754110+00:00 heroku[web.1]: Process exited with status 127
2018-12-01T14:44:37.698979+00:00 app[web.1]: bash: gunicorn: command not found
2018-12-01T14:44:38.849504+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=ipl2018prediction.herokuapp.com request_id=xxxx fwd="x.x.x.x" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T14:44:41.001548+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ipl2018prediction.herokuapp.com request_id=xxxx fwd="x.x.x.x" dyno= connect= service= status=503 bytes= protocol=https