Skip to content
This repository has been archived by the owner on Apr 1, 2020. It is now read-only.

Commit

Permalink
Add warning that django-secure is now unsupported and un-maintained.
Browse files Browse the repository at this point in the history
  • Loading branch information
carljm committed Nov 20, 2015
1 parent ef1ce78 commit 8bc412c
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@
django-secure
=============

.. warning::

This project was `merged into Django 1.8`_. It does not provide any
additional checks beyond those included in Django 1.8+, so there is no
reason to use it with Django 1.8+. Since Django 1.8 is now the lowest
supported Django version, this project is now unsupported and un-maintained.

Helping you remember to do the stupid little things to improve your Django
site's security.

Expand All @@ -10,6 +17,8 @@ are entirely or mostly served over SSL (which should include anything with
user logins).

.. _Secure Coding Guidelines: https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines
.. _merged into Django 1.8: https://docs.djangoproject.com/en/1.8/releases/1.8/#security-enhancements


Quickstart
==========
Expand Down

0 comments on commit 8bc412c

Please sign in to comment.