Django-sql-explorer

Latest version: v4.2

Safety actively analyzes 623075 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 7

4.2.0

===========================
* `609`_: Tracking should be opt-in and not use the SECRET_KEY
* `610`_: Import error (sql_metadata) with 4.1 version
* `612`_: Accessing the database during app initialization
* Regex-injection vulnerability
* Improved assistant UI

4.1.0

===========================
* SQL Assistant: Built in query help via OpenAI (or LLM of choice), with relevant schema
automatically injected into the prompt. Enable by setting EXPLORER_AI_API_KEY.
* Anonymous usage telemetry. Disable by setting EXPLORER_ENABLE_ANONYMOUS_STATS to False.
* Refactor pip requirements to make 'extras' more robust and easier to manage.
* `592`_: Support user models with no email fields
* `594`_: Eliminate <script> tags to prevent potential Content Security Policy issues.

4.0.2

Not secure
===========================
* Add support for Django 5.0. Drop support for Python < 3.10.
* Basic code completion in the editor!
* Front-end must be built with Vite if installing from source.
* `565`_: Front-end modernization. CodeMirror 6. Bootstrap5. Vite-based build
* `566`_: Django 5 support & tests
* `537`_: S3 signature version support
* `562`_: Record and show whether the last run of each query was successful
* `571`_: Replace isort and flake8 with Ruff (linting)

4.0.0.beta1

===========================
* Yanked due to a packaging version issue

3.2.1

Not secure
=====================
* `539`_: Test for SET PASSWORD
* `544`_: Fix `User` primary key reference

3.2.0

=====================
* `533`_: CSRF token httponly support + s3 destination for async results

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.