bd8b2a3632
* Prevent URLs from being added to add-on summaries Also simplify implementation of NoURLsField (already used for Collection descriptions and UserProfile biographies) to only look for URLs starting with http/https, to avoid being too aggressive while also preventing URLs with TLDs bleach's hardcoded regexp doesn't know about. |
||
|---|---|---|
| .circleci | ||
| .github | ||
| deps | ||
| docker | ||
| docs | ||
| locale | ||
| logs | ||
| private | ||
| requirements | ||
| scripts | ||
| src/olympia | ||
| static | ||
| storage | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| .jshintrc | ||
| .prettierignore | ||
| .prettierrc | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| Makefile-docker | ||
| Makefile-os | ||
| README.md | ||
| babel.cfg | ||
| babeljs.cfg | ||
| conftest.py | ||
| contribute.json | ||
| docker-compose.ci.yml | ||
| docker-compose.deps.yml | ||
| docker-compose.override.yml | ||
| docker-compose.private.yml | ||
| docker-compose.yml | ||
| jest.config.js | ||
| manage.py | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| settings.py | ||
| settings_test.py | ||
README.md
:alt: Code of conduct
:target: https://github.com/mozilla/addons-server/blob/master/.github/CODE_OF_CONDUCT.md
:target: https://circleci.com/gh/mozilla/addons-server
Addons-Server
Welcome to the Addons Server repository! Please feel free to visit the web page of the current project hosted on addons.mozilla.org. If you want to install it follow our guide located in install docs. We'd love your help! You can come talk to us on Matrix #amo:mozilla.org if you have any questions.
Please report bugs here: https://github.com/mozilla/addons/issues
You can access the AMO dev environment at https://addons-dev.allizom.org/ and the AMO stage environment at https://addons.allizom.org/
% marker-for-security-bug-inclusion-do-not-remove
Security Bug Reports
This code and its associated production web page are included in the Mozilla’s web and services bug bounty program. If you find a security vulnerability, please submit it via the process outlined in the program and FAQ pages. Further technical details about this application are available from the Bug Bounty Onramp page.
Please submit all security-related bugs through Bugzilla using the web security bug form. Never submit security-related bugs through a Github Issue or by email.