Bumps [tox](https://github.com/tox-dev/tox) from 3.25.0 to 3.25.1. - [Release notes](https://github.com/tox-dev/tox/releases) - [Changelog](https://github.com/tox-dev/tox/blob/master/docs/changelog.rst) - [Commits](https://github.com/tox-dev/tox/compare/3.25.0...3.25.1) --- updated-dependencies: - dependency-name: tox dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <firstname.lastname@example.org>
|7 days ago|
|.github||3 weeks ago|
|axes||1 month ago|
|docs||1 month ago|
|tests||2 months ago|
|.gitignore||1 year ago|
|.pre-commit-config.yaml||9 months ago|
|.prospector.yaml||2 months ago|
|CHANGES.rst||1 month ago|
|CODE_OF_CONDUCT.md||9 months ago|
|LICENSE||3 years ago|
|README.rst||1 year ago|
|codecov.yml||3 years ago|
|manage.py||2 years ago|
|mypy.ini||3 years ago|
|pyproject.toml||2 months ago|
|requirements-qa.txt||1 week ago|
|requirements-test.txt||1 month ago|
|requirements.txt||7 days ago|
|setup.py||6 months ago|
Axes is a Django plugin for keeping track of suspicious login attempts for your Django based website and implementing simple brute-force attack blocking.
The name is sort of a geeky pun, since it can be interpreted as:
access, as in monitoring access attempts, or
axes, as in tools you can use to hack (generally on wood).
Axes records login attempts to your Django powered site and prevents attackers from attempting further logins to your site when they exceed the configured attempt limit.
Axes can track the attempts and persist them in the database indefinitely, or alternatively use a fast and DDoS resistant cache implementation.
Axes can be configured to monitor login attempts by IP address, username, user agent, or their combinations.
Axes supports cool off periods, IP address whitelisting and blacklisting, user account whitelisting, and other features for Django access management.
For more information on installation and configuration see the documentation at:
If you have questions or have trouble using the app please file a bug report at:
All contributions are welcome!
It is best to separate proposed changes and PRs into small, distinct patches by type so that they can be merged faster into upstream and released quicker.
One way to organize contributions would be to separate PRs for e.g.
- new features,
- code and design improvements,
- documentation improvements, or
- tooling and CI improvements.
Merging contributions requires passing the checks configured with the CI. This includes running tests and linters successfully on the currently officially supported Python and Django versions.
The test automation is run automatically with GitHub Actions, but you can run it locally with the
tox command before pushing commits.