Answer: The latest version of bcrypt is 5.0.0, released on 2025-09-25.
Status: Confirmed
Entry: version/bcrypt
Revision: 1
Digest: sha256:96263bfdf11d1d8f (changes whenever the content changes)

Timeline:
  Created: 2026-11-12T11:23:43Z
  Last changed: 2026-11-12T11:23:43Z
  Last verified: 2026-11-12T11:33:55Z
  Next check: 2026-11-13T11:33:55Z
  Check interval: Daily
  Expected change: New releases are published at no fixed schedule.

Data:
  Field | Value | Source | As of
  Latest version | 5.0.0 | [1] | 2026-11-12
  Released | Thu, 25 Sep 2025 19:49:05 GMT | [1] | 2026-11-12

Sources:
  [1] PyPI (bcrypt). "bcrypt: release information". https://pypi.org/rss/project/bcrypt/releases.xml
      Role: primary. Accessed: 2026-11-12T11:33:55Z
      Quote: "<title>5.0.0</title>" (Supports: Latest version)
      Quote: "0/</link>
      <description>Modern password hashing for your software and your servers</description>
<author>cryptography-dev@python.org</author>      <pubDate>Thu, 25 Sep 2025 19:49:05 GMT</pubDate>" (Supports: Released)
      Snapshot SHA-256: 78d55fc4c3385d842344a3884ad86cbc652214006ece5ded57e7ddabdaac934a (captured 2026-11-12T11:23:43Z)

Verification:
  Method: Read by code directly from the structured data published at [1]; no language model was involved. Every value appears verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-12T11:23:43Z, so the values verified then were kept.
  Cross-check: not-available at 2026-11-12T11:33:55Z. No independent second source is configured for this entry
  Last successful check: 2026-11-12T11:33:55Z
  Last attempt: 2026-11-12T11:33:55Z

Notes and limitations:
  "Latest version" is the newest stable version in the registry; pre-releases are excluded.

Change log:
  Time | Event | Change | Source
  2026-11-12T11:23:43Z | added | Entry created | —
  Changes for this entry as a feed: https://latestn.com/version/bcrypt/latest

Challenge this entry:
  Open challenges: None
  How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so.
  Form: https://latestn.com/dispute/version/bcrypt
  POST: https://latestn.com/dispute/version/bcrypt with claim, evidence_url, and optionally field and contact (form-encoded or JSON)
  GET: https://latestn.com/dispute/version/bcrypt?claim={what is wrong}&evidence_url={link}

How to cite:
    latestN. (2026). What is the latest version of bcrypt? Revision 1, last verified 2026-11-12T11:33:55Z. https://latestn.com/version/bcrypt (accessed 2026-11-12T12:50:47Z).

    @misc{latestN_version_bcrypt_r1,
      title        = {What is the latest version of bcrypt?},
      author       = {{latestN}},
      year         = {2026},
      howpublished = {\url{https://latestn.com/version/bcrypt}},
      note         = {Revision 1; digest sha256:96263bfdf11d1d8f; last verified 2026-11-12T11:33:55Z; accessed 2026-11-12T12:50:47Z}
    }

URL: https://latestn.com/version/bcrypt