Vulnerability Database · PyPI · Package report

djust: vulnerability history, versions and safety

djust is a package in the PyPI ecosystem. Vulert records 29 vulnerabilities for it across 48 releases, from Aug 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
29 vulnerabilities recorded C1 H11 M3 L1 U13
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
29 in the last 12 months

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on djust 1.2.6 i

Updated on 23 Oct 2026

Good news: 1.2.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 29.

Package health score 46/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on 1.2.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.2.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.2.6 — unaffected i
  • Vulnerabilities on record 29 over 1 year · 29 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Stars 101 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for djust, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.3.0rc10 16 Oct 2026 none MIT — Details →
1.2.6 16 Oct 2026 none MIT — Details →
1.0.12 16 Oct 2026 H2 MIT Yes Details →
1.1.9 16 Oct 2026 none MIT — Details →
1.2.5 15 Oct 2026 none MIT — Details →
1.3.0rc9 15 Oct 2026 none MIT — Details →
1.0.11 15 Oct 2026 H2 MIT Yes Details →
1.1.8 15 Oct 2026 none MIT — Details →
1.2.4 15 Oct 2026 none MIT — Details →
1.0.10 11 Oct 2026 H2 MIT Yes Details →
1.1.7 11 Oct 2026 none MIT — Details →
1.3.0rc8 11 Oct 2026 none MIT — Details →
1.0.9 03 Oct 2026 L1 MIT Yes Details →
1.1.6 03 Oct 2026 none MIT — Details →
1.2.3 03 Oct 2026 none MIT — Details →
1.3.0rc7 03 Oct 2026 none MIT — Details →
1.3.0rc6 28 Sep 2026 none MIT — Details →
1.3.0rc5 27 Sep 2026 none MIT — Details →
1.3.0rc4 26 Sep 2026 none MIT — Details →
1.2.2 25 Sep 2026 none MIT — Details →
1.1.5 24 Sep 2026 none MIT — Details →
1.2.1 24 Sep 2026 none MIT — Details →
1.2.1rc2 24 Sep 2026 none MIT — Details →
1.2.1rc1 24 Sep 2026 none MIT — Details →
1.1.4 23 Sep 2026 none MIT — Details →
1.2.0 23 Sep 2026 none MIT — Details →
1.1.3 15 Sep 2026 none MIT — Details →
1.1.2 30 Aug 2026 none MIT — Details →
1.1.1 30 Aug 2026 H1 MIT Yes Details →
1.1.0 23 Aug 2026 H2 MIT Yes Details →
1.0.8 23 Jun 2026 H2 L1 MIT Yes Details →
1.0.7 22 Jun 2026 H2 L1 MIT Yes Details →
1.0.6 18 Jun 2026 C1 H10 M3 L1 U12 MIT Yes Details →
1.0.5 15 Jun 2026 C1 H10 M3 L1 U12 MIT Yes Details →
1.0.4 14 Jun 2026 C1 H10 M3 L1 U12 MIT Yes Details →
1.0.3 08 Jun 2026 C1 H11 M3 L1 U13 MIT Yes Details →
1.0.2 07 Jun 2026 C1 H11 M3 L1 U13 MIT Yes Details →
1.0.1 05 Jun 2026 C1 H11 M3 L1 U13 MIT Yes Details →
1.0.0 02 Jun 2026 C1 H11 M3 L1 U13 MIT Yes Details →
1.0.0rc11 25 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.7 17 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.6 12 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.5 07 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.4 06 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.2 02 May 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.1 30 Apr 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.9.0 29 Apr 2026 C1 H11 M3 L1 U13 MIT Yes Details →
0.4.4 15 Apr 2026 C1 H11 M3 U13 MIT Yes Details →
0.4.3 14 Apr 2026 C1 H11 M3 U13 MIT Yes Details →
0.4.2 13 Apr 2026 C1 H11 M3 U13 MIT Yes Details →
0.4.1 11 Apr 2026 C1 H11 M3 U13 MIT Yes Details →
0.4.0 27 Mar 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.8 19 Mar 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.7 16 Mar 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.6 14 Mar 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.5 05 Mar 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.4 25 Feb 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.2 18 Feb 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.1 14 Feb 2026 C1 H11 M3 U13 MIT Yes Details →
0.3.0 14 Feb 2026 C1 H11 M3 U13 MIT Yes Details →
0.2.2 01 Feb 2026 C1 H11 M3 U13 MIT Yes Details →
0.2.1 29 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.2.0 29 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.9 27 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.8 26 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.7 25 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.6 25 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.5 23 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.4 22 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.3 22 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.2 16 Jan 2026 C1 H11 M3 U13 MIT Yes Details →
0.1.0 16 Jan 2026 C1 H11 M3 U13 MIT Yes Details →

All 72 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 29

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 29 of the 29 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About djust

Is djust safe to use?

Vulert records 29 vulnerabilities for djust in PyPI: 1 critical, 11 high, 3 medium and 1 low, plus 13 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is djust's Vulert package health score?

Vulert scores djust 46/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of djust affected?

No. 1.2.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of djust should I use?

1.2.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does djust have?

29 vulnerabilities are recorded for djust in the PyPI ecosystem: 1 critical, 11 high, 3 medium and 1 low, plus 13 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new djust vulnerabilities disclosed?

29 vulnerabilities were recorded for djust in the last 12 months, and the oldest entry in this database dates to 25 Aug 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of djust are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor djust for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the djust version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.