VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

datasette-graphql: vulnerability history, versions and safety

datasette-graphql is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 25 releases, first recorded in Nov 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all datasette-graphql vulnerabilities

Vulert verdict on datasette-graphql 2.2.0 i

Updated on 23 Oct 2026

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

Package health score 59/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 2.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Nov 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 111 i
  • OpenSSF scorecard 3/10 i
  • Last release 43 months ago i
  • Licence Apache-2.0 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 datasette-graphql, 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
3.0.0a1 08 Apr 2026 none Apache-2.0 — Details →
3.0.0a0 07 Sep 2023 none Apache-2.0 — Details →
2.2.0 23 Mar 2023 none Apache-2.0 — Details →
2.1.2 19 Nov 2022 none Apache-2.0 — Details →
2.1.1 18 Jul 2022 none Apache-2.0 — Details →
2.1.0 03 Jul 2022 none Apache-2.0 — Details →
2.0.2 30 May 2022 none Apache-2.0 — Details →
2.0.1 12 Jan 2022 none Apache-2.0 — Details →
2.0.0 17 Nov 2021 none Apache-2.0 — Details →
1.5.0 16 Jul 2021 none Apache-2.0 — Details →
1.4.0 18 Feb 2021 none Apache-2.0 — Details →
1.3.1 30 Nov 2020 none Apache-2.0 — Details →
1.3.0 30 Nov 2020 none Apache-2.0 — Details →
1.2.1 24 Nov 2020 none Apache-2.0 — Details →
1.2.0 21 Nov 2020 none Apache-2.0 — Details →
1.1.0 01 Nov 2020 L1 Apache-2.0 Yes Details →
1.0.1 24 Aug 2020 L1 Apache-2.0 Yes Details →
1.0.0 23 Aug 2020 L1 Apache-2.0 Yes Details →
0.15.0 23 Aug 2020 L1 Apache-2.0 Yes Details →
0.14.0 20 Aug 2020 L1 Apache-2.0 Yes Details →
0.13.0 19 Aug 2020 L1 Apache-2.0 Yes Details →
0.12.3 19 Aug 2020 L1 Apache-2.0 Yes Details →
0.12.2 16 Aug 2020 L1 Apache-2.0 Yes Details →
0.12.1 13 Aug 2020 L1 Apache-2.0 Yes Details →
0.12.0 13 Aug 2020 L1 Apache-2.0 Yes Details →
0.11.0 09 Aug 2020 L1 Apache-2.0 Yes Details →
0.10.0 08 Aug 2020 L1 Apache-2.0 Yes Details →
0.9.0 08 Aug 2020 L1 Apache-2.0 Yes Details →
0.8.0 07 Aug 2020 L1 Apache-2.0 Yes Details →
0.7.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.6.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.5.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.4.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.3.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.2.0 06 Aug 2020 L1 Apache-2.0 Yes Details →
0.1.0a4 04 Aug 2020 L1 Apache-2.0 Yes Details →
0.1.0a3 02 Aug 2020 L1 Apache-2.0 Yes Details →
0.1.0a2 02 Aug 2020 L1 Apache-2.0 Yes Details →
0.1.0a1 02 Aug 2020 L1 Apache-2.0 Yes Details →
0.1.0a0 02 Aug 2020 L1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for datasette-graphql

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Exposed Schema of Private Database Files in datasette-graphql N/A low 1.2 24 Nov 2020

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 datasette-graphql

Is datasette-graphql safe to use?

Vulert records 1 vulnerabilities for datasette-graphql in PyPI: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is datasette-graphql's Vulert package health score?

Vulert scores datasette-graphql 59/100, which reads as usable, but worth attention. 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 datasette-graphql affected?

No. 2.2.0, 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 datasette-graphql should I use?

2.2.0 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 datasette-graphql have?

1 vulnerability is recorded for datasette-graphql in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new datasette-graphql vulnerabilities disclosed?

0 vulnerabilities were recorded for datasette-graphql in the last 12 months, and the oldest entry in this database dates to 24 Nov 2020. 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 datasette-graphql 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 datasette-graphql for upcoming vulnerabilities?

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