Not working for new Django releases
See original GitHub issue- safety version: 1.8.5
- Python version: 3.7.2
- Operating System: Ubuntu 16.04
Description
I’m trying to verify that safety
knowns about Django
security releases.
What I Did
$ cat req.txt
Django==2.2.1
Flask==0.12.2
$ safety check -r req.txt
# It reports `flask` but not `Django`.
I understand that the free database is not always up to date but the Flask security report was published 2019-07-17
and it worked for that. But Django==2.2.2
was released 2019-06-03
.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Troubleshooting - Django documentation
This page contains some advice about errors and problems commonly encountered during the development of Django applications.
Read more >Problem upgrading django doesn't show latest version
I think you're using python 2.7 which does not support this version of Django,the last version to support Python 2.7 is Django 1.11...
Read more >Release Notes - Django REST framework
Upgrade Bootstrap to 3.4.0 to resolve XSS issue. Resolve issues with composable permissions. #6299; Respect limit_choices_to on foreign keys. #6371. 3.9.
Read more >Setting up a Django development environment - MDN Web Docs
Where can we download Django? · The Python Package Repository (PyPi), using the pip tool. This is the best way to get the...
Read more >Deploying a Django application to Elastic Beanstalk
The Django version you install must be compatible with the Python version on ... work of updating your instances and starting your new...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same problem here. I’m on a paid plan, but safety ignores new Django patches. Tried to contact support, but they do not respond.
Still does not work. Does not detect e.g. CVE-2019-14235 (Django <2.2.4) or CVE-2019-14234.