VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

newsletter: vulnerability history, versions and safety

newsletter is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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 newsletter vulnerabilities

Vulert verdict on newsletter 0.1.22rc0 i

Updated on 23 Oct 2026

Good news: 0.1.22rc0, the version you would install today, has no known vulnerabilities.

Package health score 55/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 0.1.22rc0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 152 months ago i
  • Licence non-standard 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 newsletter, 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
0.1.22rc0 28 Jan 2014 none non-standard — Details →
0.1.21rc0 10 Jan 2014 none non-standard — Details →
0.1.20rc0 12 Sep 2011 none non-standard — Details →
0.1.19rc0 09 Sep 2011 none non-standard — Details →
0.1.18rc0 08 Sep 2011 none non-standard — Details →
0.1.17rc0 08 Sep 2011 none non-standard — Details →
0.1.16rc0 01 Sep 2011 none non-standard — Details →
0.1.15rc0 01 Sep 2011 none non-standard — Details →
0.1.14rc0 01 Sep 2011 none non-standard — Details →
0.1.13rc0 31 Aug 2011 none non-standard — Details →
0.1.12rc0 25 Jul 2011 none non-standard — Details →
0.1.11rc0 17 Jul 2011 none non-standard — Details →
0.1.10rc0 06 Jun 2011 none non-standard — Details →
0.1.8rc0 23 May 2011 none non-standard — Details →
0.1.7rc0 21 May 2011 none non-standard — Details →
0.1.6rc0 21 May 2011 none non-standard — Details →
0.1.5rc0 17 Apr 2011 none non-standard — Details →
0.1.4rc0 26 Mar 2011 none non-standard — Details →
0.1.3rc0 22 Mar 2011 none non-standard — Details →
0.1.2rc0 18 Mar 2011 none non-standard — Details →
0.1.1rc0 16 Mar 2011 none non-standard — Details →
0.1.0rc0 15 Mar 2011 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for newsletter

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 newsletter

Is newsletter safe to use?

Vulert has no vulnerabilities on record for newsletter in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is newsletter's Vulert package health score?

Vulert scores newsletter 55/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 newsletter affected?

No. 0.1.22rc0, 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 newsletter should I use?

0.1.22rc0 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 newsletter have?

0 vulnerabilities are recorded for newsletter in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new newsletter vulnerabilities disclosed?

0 vulnerabilities were recorded for newsletter in the last 12 months. 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 newsletter 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 newsletter for upcoming vulnerabilities?

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