VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

oncall: vulnerability history, versions and safety

oncall is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 20 releases, from Feb 2021 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
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 oncall vulnerabilities

Vulert verdict on oncall 2.1.7 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.1.7 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 30 Apr 2021 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 1,258 i
  • OpenSSF scorecard 2/10 i
  • Last release 31 months ago i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 oncall, 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
2.1.7 12 Mar 2024 none BSD-2-Clause — Details →
2.1.6 12 Mar 2024 none BSD-2-Clause — Details →
2.1.5 18 Dec 2023 none BSD-2-Clause — Details →
2.0.5 22 Nov 2023 none BSD-2-Clause — Details →
2.0.4 02 Oct 2023 none BSD-2-Clause — Details →
2.0.3 02 Oct 2023 none BSD-2-Clause — Details →
2.0.2 02 Oct 2023 none BSD-2-Clause — Details →
2.0.1 07 Jun 2023 none BSD-2-Clause — Details →
2.0.0 07 Jun 2023 none BSD-2-Clause — Details →
1.5.5 03 May 2023 none BSD-2-Clause — Details →
1.5.4 04 Apr 2023 none BSD-2-Clause — Details →
1.5.3 05 Jan 2023 none BSD-2-Clause — Details →
1.5.2 05 Jan 2023 none BSD-2-Clause — Details →
1.5.1 07 Dec 2022 none BSD-2-Clause — Details →
1.5.0 07 Dec 2022 none BSD-2-Clause — Details →
1.4.5 27 Apr 2022 none BSD-2-Clause — Details →
1.4.4 29 Mar 2022 none BSD-2-Clause — Details →
1.4.3 09 Jun 2021 none non-standard — Details →
1.4.2 04 Jun 2021 none non-standard — Details →
1.4.1 06 Feb 2021 none non-standard — Details →
1.4.0 29 Jan 2021 M1 U1 non-standard Yes Details →
1.3.9 28 Jan 2021 M1 U1 non-standard Yes Details →
1.3.8 28 Jan 2021 M1 U1 non-standard Yes Details →
1.3.7 26 Jan 2021 M1 U1 non-standard Yes Details →
1.3.6 25 Jan 2021 M1 U1 non-standard Yes Details →
1.3.5 07 Dec 2020 M1 U1 non-standard Yes Details →
1.3.4 07 Dec 2020 M1 U1 non-standard Yes Details →
1.2.4 02 Oct 2020 M1 U1 non-standard Yes Details →
1.2.3 23 Apr 2020 M1 U1 non-standard Yes Details →
1.2.2 15 Apr 2020 M1 U1 non-standard Yes Details →
1.2.1 30 Mar 2020 M1 U1 non-standard Yes Details →
1.2.0 30 Mar 2020 M1 U1 non-standard Yes Details →
1.1.10 16 Mar 2020 M1 U1 non-standard Yes Details →
1.1.9 12 Mar 2020 M1 U1 non-standard Yes Details →
1.1.8 10 Mar 2020 M1 U1 non-standard Yes Details →
1.1.7 04 Feb 2020 M1 U1 non-standard Yes Details →
1.1.5 04 Feb 2020 M1 U1 non-standard Yes Details →
1.1.4 30 Jan 2020 M1 U1 non-standard Yes Details →
1.1.3 24 Jan 2020 M1 U1 non-standard Yes Details →
1.1.2 24 Jan 2020 M1 U1 — 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

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for oncall

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-26722: Cross-Site Scripting in LinkedIn Oncall 6.1 medium 1.4.1 30 Apr 2021
CVE-2021-26722: LinkedIn Oncall Reflected XSS Vulnerability N/A unrated 1.4.1 05 Feb 2021

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 oncall

Is oncall safe to use?

Vulert records 2 vulnerabilities for oncall in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 oncall's Vulert package health score?

Vulert scores oncall 63/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 oncall affected?

No. 2.1.7, 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 oncall should I use?

2.1.7 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 oncall have?

2 vulnerabilities are recorded for oncall in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 oncall vulnerabilities disclosed?

0 vulnerabilities were recorded for oncall in the last 12 months, and the oldest entry in this database dates to 05 Feb 2021. 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 oncall 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 oncall for upcoming vulnerabilities?

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