VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pycep-parser: vulnerability history, versions and safety

pycep-parser 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 pycep-parser vulnerabilities

Vulert verdict on pycep-parser 0.7.1 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 0.7.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 14 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 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 pycep-parser, 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.7.1 09 Aug 2026 none Apache-2.0 — Details →
0.7.1.dev11 09 Aug 2026 none Apache-2.0 — Details →
0.7.1.dev10 09 Aug 2026 none Apache-2.0 — Details →
0.7.1.dev9 14 Jun 2026 none Apache-2.0 — Details →
0.7.1.dev8 29 May 2026 none Apache-2.0 — Details →
0.7.1.dev7 21 Apr 2026 none Apache-2.0 — Details →
0.7.1.dev6 04 Apr 2026 none Apache-2.0 — Details →
0.7.1.dev5 28 Feb 2026 none Apache-2.0 — Details →
0.7.1.dev4 15 Feb 2026 none Apache-2.0 — Details →
0.7.1.dev3 09 Feb 2026 none Apache-2.0 — Details →
0.7.0 10 Jan 2026 none Apache-2.0 — Details →
0.7.0.dev9 10 Jan 2026 none Apache-2.0 — Details →
0.7.0.dev8 01 Jan 2026 none Apache-2.0 — Details →
0.7.0.dev7 27 Dec 2025 none Apache-2.0 — Details →
0.7.0.dev6 18 Dec 2025 none Apache-2.0 — Details →
0.7.0.dev5 28 Nov 2025 none Apache-2.0 — Details →
0.7.0.dev4 27 Nov 2025 none Apache-2.0 — Details →
0.7.0.dev3 23 Nov 2025 none Apache-2.0 — Details →
0.7.0.dev2 23 Nov 2025 none Apache-2.0 — Details →
0.7.0.dev1 23 Nov 2025 none Apache-2.0 — Details →
0.6.1 23 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev9 15 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev8 15 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev7 15 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev6 11 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev5 02 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev4 02 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev3 02 Nov 2025 none Apache-2.0 — Details →
0.6.1.dev2 02 Nov 2025 none Apache-2.0 — Details →
0.6.1a0 01 Dec 2024 none Apache-2.0 — Details →
0.5.1 03 Nov 2024 none Apache-2.0 — Details →
0.5.1a9 03 Nov 2024 none Apache-2.0 — Details →
0.5.1a8 31 Oct 2024 none Apache-2.0 — Details →
0.5.1a7 31 Oct 2024 none Apache-2.0 — Details →
0.5.1a6 23 Oct 2024 none Apache-2.0 — Details →
0.5.1a5 30 Jul 2024 none Apache-2.0 — Details →
0.5.1a4 13 Apr 2024 none Apache-2.0 — Details →
0.5.1a3 09 Apr 2024 none Apache-2.0 — Details →
0.5.1a2 09 Apr 2024 none Apache-2.0 — Details →
0.5.1a1 05 Nov 2023 none Apache-2.0 — Details →
0.5.1a0 05 Nov 2023 none Apache-2.0 — Details →
0.4.2 05 Nov 2023 none Apache-2.0 — Details →
0.4.2a2 05 Nov 2023 none Apache-2.0 — Details →
0.4.2a1 05 Nov 2023 none Apache-2.0 — Details →
0.4.2a0 10 Aug 2023 none Apache-2.0 — Details →
0.4.1 18 Jun 2023 none Apache-2.0 — Details →
0.4.1a0 18 Jun 2023 none Apache-2.0 — Details →
0.4.0 30 Apr 2023 none Apache-2.0 — Details →
0.3.10a7 30 Apr 2023 none Apache-2.0 — Details →
0.3.10a6 29 Apr 2023 none Apache-2.0 — Details →
0.3.10a5 07 Apr 2023 none Apache-2.0 — Details →
0.3.10a4 01 Apr 2023 none Apache-2.0 — Details →
0.3.10a3 15 Jan 2023 none Apache-2.0 — Details →
0.3.10a2 20 Nov 2022 none Apache-2.0 — Details →
0.3.10a1 20 Nov 2022 none Apache-2.0 — Details →
0.3.10a0 20 Nov 2022 none Apache-2.0 — Details →
0.3.9 31 Aug 2022 none Apache-2.0 — Details →
0.3.9a3 30 Aug 2022 none Apache-2.0 — Details →
0.3.9a2 30 Aug 2022 none Apache-2.0 — Details →
0.3.9a1 30 Aug 2022 none Apache-2.0 — Details →
0.3.9a0 30 Aug 2022 none Apache-2.0 — Details →
0.3.8 01 Aug 2022 none Apache-2.0 — Details →
0.3.8a3 01 Aug 2022 none Apache-2.0 — Details →
0.3.8a2 09 Jul 2022 none Apache-2.0 — Details →
0.3.8a1 08 Jul 2022 none Apache-2.0 — Details →
0.3.8a0 25 Jun 2022 none Apache-2.0 — Details →
0.3.7 04 Jun 2022 none Apache-2.0 — Details →
0.3.7a3 04 Jun 2022 none Apache-2.0 — Details →
0.3.7a2 04 Jun 2022 none Apache-2.0 — Details →
0.3.7a1 03 Jun 2022 none Apache-2.0 — Details →
0.3.7a0 03 Jun 2022 none Apache-2.0 — Details →
0.3.6 21 May 2022 none Apache-2.0 — Details →
0.3.6a1 21 May 2022 none Apache-2.0 — Details →
0.3.6a0 17 May 2022 none Apache-2.0 — Details →
0.3.5 15 May 2022 none Apache-2.0 — Details →
0.3.5a2 15 May 2022 none Apache-2.0 — Details →
0.3.5a1 15 May 2022 none Apache-2.0 — Details →
0.3.5a0 13 May 2022 none Apache-2.0 — Details →
0.3.4 10 Apr 2022 none Apache-2.0 — Details →
0.3.4a3 10 Apr 2022 none Apache-2.0 — Details →
0.3.4a2 10 Apr 2022 none Apache-2.0 — Details →
0.3.4a1 05 Apr 2022 none Apache-2.0 — Details →
0.3.4a0 05 Apr 2022 none Apache-2.0 — Details →
0.3.3 21 Mar 2022 none Apache-2.0 — Details →
0.3.3a0 21 Mar 2022 none Apache-2.0 — Details →
0.3.2 14 Mar 2022 none Apache-2.0 — Details →
0.3.2a4 14 Mar 2022 none Apache-2.0 — Details →
0.3.2a3 09 Mar 2022 none Apache-2.0 — Details →
0.3.2a2 08 Mar 2022 none Apache-2.0 — Details →
0.3.2a1 06 Mar 2022 none Apache-2.0 — Details →
0.3.2a0 06 Mar 2022 none Apache-2.0 — Details →
0.3.1 05 Mar 2022 none Apache-2.0 — Details →
0.3.1a1 05 Mar 2022 none Apache-2.0 — Details →
0.3.1a0 05 Mar 2022 none Apache-2.0 — Details →
0.3.0 03 Mar 2022 none Apache-2.0 — Details →
0.2.1a9 03 Mar 2022 none Apache-2.0 — Details →
0.2.1a8 02 Mar 2022 none Apache-2.0 — Details →
0.2.1a7 28 Feb 2022 none Apache-2.0 — Details →
0.2.1a6 28 Feb 2022 none Apache-2.0 — Details →
0.2.1a5 26 Feb 2022 none Apache-2.0 — Details →
0.2.1a4 26 Feb 2022 none — — Details →
0.2.1a3 23 Feb 2022 none — — Details →
0.2.1a2 20 Feb 2022 none — — Details →
0.2.1a1 19 Feb 2022 none — — Details →
0.2.1a0 19 Feb 2022 none — — Details →
0.2.0 13 Feb 2022 none — — Details →
0.1.1a6 13 Feb 2022 none — — Details →
0.1.1a5 09 Feb 2022 none — — Details →
0.1.1a4 07 Feb 2022 none — — Details →
0.1.1a3 06 Feb 2022 none — — Details →
0.1.1a2 06 Feb 2022 none — — Details →
0.1.1a1 06 Feb 2022 none — — Details →
0.1.1a0 06 Feb 2022 none — — Details →
0.1.0 06 Feb 2022 none — — Details →
0.0.1a31 06 Feb 2022 none — — Details →
0.0.1a30 05 Feb 2022 none — — Details →
0.0.1a29 04 Feb 2022 none — — Details →
0.0.1a28 04 Feb 2022 none — — Details →
0.0.1a27 03 Feb 2022 none — — Details →
0.0.1a26 01 Feb 2022 none — — Details →

The newest 120 of 146 versions Vulert tracks. 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 pycep-parser

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 pycep-parser

Is pycep-parser safe to use?

Vulert has no vulnerabilities on record for pycep-parser 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 pycep-parser's Vulert package health score?

Vulert scores pycep-parser 71/100, which reads as in good shape. 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 pycep-parser affected?

No. 0.7.1, 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 pycep-parser should I use?

0.7.1 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 pycep-parser have?

0 vulnerabilities are recorded for pycep-parser 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 pycep-parser vulnerabilities disclosed?

0 vulnerabilities were recorded for pycep-parser 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 pycep-parser 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 pycep-parser for upcoming vulnerabilities?

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