VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

replicate: vulnerability history, versions and safety

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

Vulert verdict on replicate 1.0.7 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 1.0.7 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 72 packages i
  • Stars 3 i
  • Last release 16 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 replicate, 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.0.0b4 18 Dec 2025 none Apache-2.0 — Details →
2.0.0b3 16 Nov 2025 none Apache-2.0 — Details →
2.0.0b2 24 Oct 2025 none Apache-2.0 — Details →
2.0.0b1 23 Oct 2025 none Apache-2.0 — Details →
2.0.0a31 22 Oct 2025 none Apache-2.0 — Details →
2.0.0a30 15 Oct 2025 none Apache-2.0 — Details →
2.0.0a29 15 Oct 2025 none Apache-2.0 — Details →
2.0.0a28 07 Oct 2025 none Apache-2.0 — Details →
2.0.0a27 29 Sep 2025 none Apache-2.0 — Details →
2.0.0a26 17 Sep 2025 none Apache-2.0 — Details →
2.0.0a25 15 Sep 2025 none Apache-2.0 — Details →
2.0.0a24 12 Sep 2025 none Apache-2.0 — Details →
2.0.0a23 04 Sep 2025 none Apache-2.0 — Details →
2.0.0a22 28 Aug 2025 none Apache-2.0 — Details →
2.0.0a21 27 Aug 2025 none Apache-2.0 — Details →
1.1.0b3 26 Aug 2025 none non-standard — Details →
2.0.0a20 25 Aug 2025 none Apache-2.0 — Details →
2.0.0a19 22 Aug 2025 none Apache-2.0 — Details →
2.0.0a18 20 Aug 2025 none Apache-2.0 — Details →
2.0.0a17 12 Aug 2025 none Apache-2.0 — Details →
2.0.0a16 11 Aug 2025 none Apache-2.0 — Details →
2.0.0a15 06 Aug 2025 none Apache-2.0 — Details →
2.0.0a14 31 Jul 2025 none Apache-2.0 — Details →
2.0.0a13 25 Jul 2025 none Apache-2.0 — Details →
2.0.0a12 23 Jul 2025 none Apache-2.0 — Details →
2.0.0a11 12 Jul 2025 none Apache-2.0 — Details →
2.0.0a10 08 Jul 2025 none Apache-2.0 — Details →
2.0.0a9 02 Jul 2025 none Apache-2.0 — Details →
2.0.0a8 30 Jun 2025 none Apache-2.0 — Details →
2.0.0a7 27 Jun 2025 none Apache-2.0 — Details →
2.0.0a6 26 Jun 2025 none Apache-2.0 — Details →
2.0.0a5 25 Jun 2025 none Apache-2.0 — Details →
2.0.0a4 18 Jun 2025 none Apache-2.0 — Details →
2.0.0a3 17 Jun 2025 none Apache-2.0 — Details →
2.0.0a2 16 Jun 2025 none Apache-2.0 — Details →
1.1.0b2 12 Jun 2025 none non-standard — Details →
2.0.0a1 10 Jun 2025 none Apache-2.0 — Details →
1.1.0b1 09 Jun 2025 none non-standard — Details →
1.0.7 27 May 2025 none non-standard — Details →
1.0.6 25 Apr 2025 none non-standard — Details →
1.0.4 25 Nov 2024 none non-standard — Details →
1.0.3 28 Oct 2024 none non-standard — Details →
1.0.2 16 Oct 2024 none non-standard — Details →
1.0.1 09 Oct 2024 none non-standard — Details →
1.0.0 09 Oct 2024 none non-standard — Details →
1.0.0b3 05 Oct 2024 none non-standard — Details →
1.0.0b2 04 Oct 2024 none non-standard — Details →
1.0.0b1 04 Oct 2024 none non-standard — Details →
0.34.2 04 Oct 2024 none non-standard — Details →
0.34.1 25 Sep 2024 none non-standard — Details →
0.34.0 25 Sep 2024 none non-standard — Details →
0.33.0 16 Sep 2024 none non-standard — Details →
0.32.1 30 Aug 2024 none non-standard — Details →
0.32.0 22 Aug 2024 none non-standard — Details →
0.31.0 31 Jul 2024 none non-standard — Details →
0.30.1 25 Jul 2024 none non-standard — Details →
0.30.0 25 Jul 2024 none non-standard — Details →
0.29.0 18 Jul 2024 none non-standard — Details →
0.28.0 05 Jul 2024 none non-standard — Details →
0.27.0 28 Jun 2024 none non-standard — Details →
0.26.1 21 Jun 2024 none non-standard — Details →
0.26.0 14 May 2024 none non-standard — Details →
0.25.2 19 Apr 2024 none non-standard — Details →
0.25.1 21 Mar 2024 none non-standard — Details →
0.25.0 19 Mar 2024 none non-standard — Details →
0.24.0 19 Feb 2024 none non-standard — Details →
0.23.1 27 Jan 2024 none non-standard — Details →
0.23.0 23 Jan 2024 none non-standard — Details →
0.22.0 08 Dec 2023 none non-standard — Details →
0.21.1 04 Dec 2023 none non-standard — Details →
0.21.0 27 Nov 2023 none non-standard — Details →
0.20.0 17 Nov 2023 none non-standard — Details →
0.19.0 16 Nov 2023 none non-standard — Details →
0.18.1 09 Nov 2023 none non-standard — Details →
0.18.0 09 Nov 2023 none non-standard — Details →
0.17.0 07 Nov 2023 none non-standard — Details →
0.16.0 06 Nov 2023 none non-standard — Details →
0.15.8 05 Nov 2023 none non-standard — Details →
0.15.7 02 Nov 2023 none non-standard — Details →
0.15.6 02 Nov 2023 none non-standard — Details →
0.15.5 29 Oct 2023 none non-standard — Details →
0.15.4 09 Oct 2023 none non-standard — Details →
0.15.3 05 Oct 2023 none non-standard — Details →
0.15.2 05 Oct 2023 none non-standard — Details →
0.15.1 04 Oct 2023 none non-standard — Details →
0.15.0 04 Oct 2023 none non-standard — Details →
0.14.0 03 Oct 2023 none non-standard — Details →
0.13.0 17 Sep 2023 none non-standard — Details →
0.12.0 11 Sep 2023 none non-standard — Details →
0.11.0 07 Aug 2023 none non-standard — Details →
0.10.0 31 Jul 2023 none non-standard — Details →
0.9.0 19 Jul 2023 none non-standard — Details →
0.8.4 04 Jul 2023 none non-standard — Details →
0.8.3 23 May 2023 none non-standard — Details →
0.8.2 19 May 2023 none non-standard — Details →
0.8.1 12 Apr 2023 none non-standard — Details →
0.8.0 12 Apr 2023 none non-standard — Details →
0.7.0 06 Apr 2023 none non-standard — Details →
0.6.1 28 Mar 2023 none non-standard — Details →
0.6.0 26 Mar 2023 none non-standard — Details →
0.5.2 15 Mar 2023 none — — Details →
0.5.1 03 Mar 2023 none — — Details →
0.5.0 20 Feb 2023 none — — Details →
0.4.0 14 Sep 2022 none — — Details →
0.0.1a16 07 Sep 2022 none — — Details →
0.0.1a15 14 Jun 2022 none — — Details →
0.0.1a14 08 Jun 2022 none — — Details →
0.0.1a13 07 Jun 2022 none — — Details →
0.0.1a12 04 Jun 2022 none — — Details →
0.0.1a11 03 Jun 2022 none — — Details →
0.0.1a10 27 May 2022 none — — Details →
0.0.1a9 25 May 2022 none — — Details →
0.0.1a8 25 May 2022 none — — Details →
0.0.1a7 19 May 2022 none — — Details →
0.0.1a6 17 May 2022 none — — Details →
0.0.1a5 17 May 2022 none — — Details →
0.0.1a4 17 May 2022 none — — Details →
0.0.1a3 17 May 2022 none — — Details →
0.0.1a2 17 May 2022 none — — Details →
0.0.1a1 17 May 2022 none — — Details →

All 120 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 replicate

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 replicate

Is replicate safe to use?

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

Vulert scores replicate 68/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 replicate affected?

No. 1.0.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 replicate should I use?

1.0.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 replicate have?

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

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

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