Open Divergence Radar Catalog Method Feedback

Is legrandin/pycryptodome the fork of pycrypto/pycrypto?

legrandin/pycryptodome subject · fork candidate fork of? pycrypto/pycrypto object · upstream base

pycryptodome-pycrypto · status observed

Data verified at: 2026-09-11T16:53:23Z (UTC)

Conclusion status

No confirmed conclusion exists for this pair. The evidence below is presented for transparency; a relationship conclusion requires a human review that has not happened, or a previous decision no longer matches the current evidence.

Evidence suggests legrandin/pycryptodome is a fork of pycrypto/pycrypto. Human review required before publication.

Seed context: Research question: is PyCryptodome the maintained continuation/fork of PyCrypto?

Evidence (1)

Verbatim excerpts from official sources, whitespace-normalized. Full payloads are hashed and retained by the pipeline; collection failures never fabricate evidence.

KindExcerptSourceRevisionFirst observed
fork_claim
PyCryptodome is a fork of PyCrypto.
 source
3efd9c64a4…3efd9c64a47127029eaa67295de785fbf554d222
 2026-09-12T02:59:28Z

Observed repository facts

As of the last verified collection. These are facts about the snapshots, not activity verdicts — a low number is not a claim that a project is inactive.

EndpointRepoStarsLast pushForkArchived
legrandin/pycryptodome Legrandin/pycryptodome 3262 2026-07-18T07:43:51Z no no
pycrypto/pycrypto pycrypto/pycrypto 2472 2022-01-26T16:04:12Z no yes

Package registry facts

PackageLatestDeprecatedDeprecation messageYanked (latest)
pypi:pycryptodome 3.23.0 — — no
pypi:pycrypto 2.6.1 — — no

Versions & deployment facts

Official release and package declarations, compared independently of the relationship verdict. These are not installation tests or a migration guarantee. Missing declarations mean unknown.

legrandin/pycryptodome

pycryptodome · 3.23.0

Official source

PyPI current version metadata. Verified: 2026-09-16T11:10:38.085Z (UTC).

Requires-Dist markers and extras are preserved, not assumed mandatory. Wheel tags describe published artifacts, not independent runtime tests. No wheel does not mean unsupported.

Runtime declarations
{
  "python": "!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*,!=3.5.*,!=3.6.*,>=2.7"
}
Operating systems
Not declared / unknown
CPU architectures
Not declared / unknown
C libraries
Not declared / unknown
Direct dependency declarations
{
  "requires_dist": null
}
Published artifacts (40)
Provenance

Parser: software-1

First observed: 2026-09-16T11:10:38.085Z (UTC)

Last checked: 2026-09-16T11:10:38.085Z (UTC)

Source response SHA-256: 6a679529a5da2d2744986190f35cedbc6c0af8ffc0d83e425f430ca5ed8c4970

GitHub release · v3.23.0

Official source

GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-09-16T11:13:53.818Z (UTC).

Listed release assets only. Asset names do not prove platform support or successful execution.

Runtime declarations
Not declared / unknown
Operating systems
Not declared / unknown
CPU architectures
Not declared / unknown
C libraries
Not declared / unknown
Direct dependency declarations
Not declared / unknown
Published artifacts (2)
Provenance

Parser: software-1

First observed: 2026-09-16T11:13:53.818Z (UTC)

Last checked: 2026-09-16T11:13:53.818Z (UTC)

Source response SHA-256: e6da62a6303eb09718c29fdf215469ee11fd178c1ee15c3a12bdcfb29e3b76bd

pycrypto/pycrypto

pycrypto · 2.6.1

Official source

PyPI current version metadata. Verified: 2026-09-16T11:10:38.085Z (UTC).

Requires-Dist markers and extras are preserved, not assumed mandatory. Wheel tags describe published artifacts, not independent runtime tests. No wheel does not mean unsupported.

Runtime declarations
Not declared / unknown
Operating systems
Not declared / unknown
CPU architectures
Not declared / unknown
C libraries
Not declared / unknown
Direct dependency declarations
{
  "requires_dist": null
}
Published artifacts (0)
    Provenance

    Parser: software-1

    First observed: 2026-09-16T11:10:38.085Z (UTC)

    Last checked: 2026-09-16T11:10:38.085Z (UTC)

    Source response SHA-256: 61a770d3d9f4f2671386f6e16ed44622e38709dbd6e7de1c0e1e7cef3bea2a99

    GitHub release · Unknown version

    Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.

    Official source

    Timeline

    “Event time” is an upstream timestamp when the source provides one; “first observed” is when this project saw it. They are deliberately separate columns.

    EventEvent timeFirst observedSource
    legrandin/pycryptodome metadata first observed — 2026-09-11T16:51:52Z link
    recent commit activity of legrandin/pycryptodome observed (5 commits in sampled window) 2025-06-28T21:06:05Z 2026-09-11T16:51:54Z link
    pycrypto/pycrypto metadata first observed — 2026-09-11T16:51:56Z link
    recent commit activity of pycrypto/pycrypto observed (5 commits in sampled window) 2022-01-25T06:57:52Z 2026-09-11T16:51:59Z link
    automatic evaluation -> needs_review — 2026-09-11T16:53:25Z —
    evidence: fork_claim — 2026-09-11T16:53:25Z link
    automatic evaluation -> needs_review — 2026-09-11T16:58:19Z —
    evidence: fork_claim — 2026-09-11T16:58:19Z link
    automatic evaluation -> needs_review — 2026-09-12T02:55:35Z —
    evidence: fork_claim — 2026-09-12T02:55:35Z link
    automatic evaluation -> needs_review — 2026-09-12T02:57:05Z —
    evidence: fork_claim — 2026-09-12T02:57:05Z link
    automatic evaluation -> needs_review — 2026-09-12T02:59:28Z —
    evidence: fork_claim — 2026-09-12T02:59:28Z link

    Decision and dispute history

    Review decisions are recorded privately with reasons that stay internal; this public history shows what happened and when, not why.

    KindWhen (UTC)
    automatic evaluation → needs_review2026-09-11T16:53:25Z
    automatic evaluation → needs_review2026-09-11T16:58:19Z
    automatic evaluation → needs_review2026-09-12T02:55:35Z
    automatic evaluation → needs_review2026-09-12T02:57:05Z
    automatic evaluation → needs_review2026-09-12T02:59:28Z

    To question this report, use the feedback form, select “data error”, and include pair ID pycryptodome-pycrypto. Feedback is reviewed privately and does not change a report automatically.

    Snapshot taken at 2026-09-16T13:11:39.533Z (UTC).