Vulnerability Database · PyPI · Package report

projen: vulnerability history, versions and safety

projen is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in 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
1 vulnerabilities recorded 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.

Vulert verdict on projen 0.104.14 i

Updated on 23 Oct 2026

Action needed: 0.104.14 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.104.14 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 06 Apr 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,958 i
  • OpenSSF scorecard 6/10 i
  • Last release this month 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 projen, 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.104.14 23 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.13 23 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.12 23 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.11 22 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.10 20 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.9 19 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.8 15 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.7 15 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.6 15 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.5 12 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.4 11 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.3 09 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.2 08 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.1 07 Oct 2026 U1 Apache-2.0 Yes Details →
0.104.0 05 Oct 2026 U1 Apache-2.0 Yes Details →
0.103.27 22 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.26 21 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.25 18 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.24 16 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.23 10 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.22 09 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.21 09 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.20 06 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.19 04 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.18 03 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.17 03 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.16 03 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.15 02 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.14 02 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.13 01 Sep 2026 U1 Apache-2.0 Yes Details →
0.103.12 31 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.11 29 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.10 28 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.9 28 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.8 28 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.7 28 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.6 28 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.5 26 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.4 26 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.3 25 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.2 24 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.1 21 Aug 2026 U1 Apache-2.0 Yes Details →
0.103.0 21 Aug 2026 U1 Apache-2.0 Yes Details →
0.102.0 21 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.37 20 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.36 20 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.35 20 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.34 20 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.33 19 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.32 18 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.31 09 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.30 08 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.29 07 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.28 07 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.27 06 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.26 05 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.25 04 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.24 04 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.23 01 Aug 2026 U1 Apache-2.0 Yes Details →
0.101.22 29 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.21 28 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.20 24 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.19 24 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.18 24 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.17 20 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.16 16 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.15 15 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.14 14 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.13 14 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.12 14 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.11 10 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.10 10 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.9 10 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.8 09 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.7 09 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.6 08 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.5 08 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.4 01 Jul 2026 U1 Apache-2.0 Yes Details →
0.101.3 30 Jun 2026 U1 Apache-2.0 Yes Details →
0.101.2 30 Jun 2026 U1 Apache-2.0 Yes Details →
0.101.1 29 Jun 2026 U1 Apache-2.0 Yes Details →
0.101.0 29 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.7 25 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.6 24 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.5 23 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.4 22 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.3 22 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.2 21 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.1 21 Jun 2026 U1 Apache-2.0 Yes Details →
0.100.0 19 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.80 18 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.79 18 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.78 18 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.77 18 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.76 17 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.75 17 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.74 12 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.73 11 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.72 11 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.71 07 Jun 2026 U1 Apache-2.0 Yes Details →
0.99.70 28 May 2026 U1 — Yes Details →
0.99.69 28 May 2026 U1 — Yes Details →
0.99.68 27 May 2026 U1 — Yes Details →
0.99.67 27 May 2026 U1 — Yes Details →
0.99.66 26 May 2026 U1 — Yes Details →
0.99.65 24 May 2026 U1 — Yes Details →
0.99.64 23 May 2026 U1 — Yes Details →
0.99.63 20 May 2026 U1 — Yes Details →
0.99.62 18 May 2026 U1 — Yes Details →
0.99.61 13 May 2026 U1 — Yes Details →
0.99.60 11 May 2026 U1 — Yes Details →
0.99.59 11 May 2026 U1 — Yes Details →
0.99.58 10 May 2026 U1 — Yes Details →
0.99.57 07 May 2026 U1 — Yes Details →
0.99.56 07 May 2026 U1 — Yes Details →
0.99.55 07 May 2026 U1 — Yes Details →
0.99.54 07 May 2026 U1 — Yes Details →
0.99.53 06 May 2026 U1 — Yes Details →
0.99.52 20 Apr 2026 U1 — Yes Details →
0.99.51 17 Apr 2026 U1 — Yes Details →

The newest 120 of 1,904 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 projen

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-21423: Vulnerability in projen package N/A unrated 36030c6a4b1acd0054673322612e7c70e9446643 06 Apr 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 projen

Is projen safe to use?

Vulert records 1 vulnerabilities for projen in PyPI: 0 critical, 0 high, 0 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 projen's Vulert package health score?

Vulert scores projen 88/100, which reads as healthy. 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 projen affected?

Yes. 0.104.14, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does projen have?

1 vulnerability is recorded for projen in the PyPI ecosystem: 0 critical, 0 high, 0 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 projen vulnerabilities disclosed?

0 vulnerabilities were recorded for projen in the last 12 months, and the oldest entry in this database dates to 06 Apr 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 projen 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 projen for upcoming vulnerabilities?

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