Open Divergence Radar Catalog Method Feedback

Is mylar3/mylar3 the successor of evilhero/mylar?

mylar3/mylar3 subject · successor candidate successor of? evilhero/mylar object · predecessor

mylar-mylar3 · status observed

Data verified at: 2026-11-09T20:01:42.969Z (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 mylar3/mylar3 may succeed evilhero/mylar (directional claim found). Human review required before publication.

Seed context: 2026-09-21 extra authorized discovery; NOT APPROVED; pending collector ingestion. Original README explicitly says development moved to Mylar3 and declares EOL; old repo archived, new repo maintained. Sources: https://github.com/evilhero/mylar and https://github.com/mylar3/mylar3. Distinct canonical IDs 5740898 -> 233701130. Raw: succession-research-20260921-extra.json.

Evidence (1)

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

successor_claim

Mylar ## Note that feature development has stopped as we have moved to Mylar3.
Source
Official source
Revision
16cb956f23…16cb956f23f53f73fc9498a55dbc9aad2d78fcee
First observed
2026-09-21T16:01:57.004Z

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
mylar3/mylar3 mylar3/mylar3 1468 2026-03-25T17:09:46Z no no
evilhero/mylar evilhero/mylar 958 2020-12-28T19:28:06Z no yes

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.

Version-scoped runtime comparison — literal declarations, not migration advice
mylar3/mylar3evilhero/mylar

Unknown: no collected package runtime declaration.

Unknown: no collected package runtime declaration.

mylar3/mylar3

Release-pinned deployment declarations

Release commit · v0.8.3 · complete

Commit: cdc94a44425b6f3f9cdb9b6e5f9d88ae2fee3316

Collection endpoint (may change) · Observed 2026-09-21T19:00:27.543Z

Observation is outside the freshness window. Immutable evidence is retained; current registry availability is unknown.

Response SHA-256: cb49912b139d683468e03d8d97e6dd0fbc24b58a8a851e23eac607bc8e6c76db

Release tree · v0.8.3 · complete

Commit: cdc94a44425b6f3f9cdb9b6e5f9d88ae2fee3316

Collection endpoint (may change) · Observed 2026-09-21T19:00:27.543Z

Observation is outside the freshness window. Immutable evidence is retained; current registry availability is unknown.

File search coverage: selected_manifest_names. Only selected manifest filenames were searched; fixtures and vendored dependency directories are excluded. Unlisted declarations remain unknown.

Response SHA-256: a3281d5b028a043f6708eb6a569a471b898f0dae07fdeabb5bea5072f7373114

Dockerfile · v0.8.3 · complete

Commit: cdc94a44425b6f3f9cdb9b6e5f9d88ae2fee3316

Commit-pinned source · Observed 2026-09-21T19:00:27.543Z

Observation is outside the freshness window. Immutable evidence is retained; current registry availability is unknown.

File context: unspecified. Package version in file: not declared.

Runtime declaration in this file
Not declared / unknown
Services and dependency roles

No service declarations extracted from this file; production requirements remain unknown.

Container configuration

python:${BASE_VERSION} · build_base_or_stage · requested platform: unknown. Requested platform is not proof of an available image.

FROM images are build-stage inputs, not proof of a published project image or minimum runtime.

Response SHA-256: ff52e1cf11f7b1cf9d4bea5f4e9aca08e59eb3d6979b6c989aa8758d7ea4d4c5

GitHub release · v0.8.3 · not_modified

Official source

GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-11-15T02:00:57.995Z (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 (0)
    Provenance

    Parser: software-1

    First observed: 2026-09-21T16:01:50.151Z (UTC)

    Last checked: 2026-11-15T02:00:57.995Z (UTC)

    Source response SHA-256: afa4dbd7c778b3aa11896fb68331f6cdbee0b8bbc7435dae413b2c2ba0bd6958

    evilhero/mylar

    Release-pinned deployment declarations

    Unknown: no release-pinned files have been collected. The default branch is not substituted.

    GitHub release · Unknown version · stale evidence

    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
    automatic evaluation -> insufficient_data — 2026-09-21T14:37:31.042Z —
    mylar3/mylar3 metadata first observed — 2026-09-21T16:01:47.195Z link
    recent commit activity of mylar3/mylar3 observed (5 commits in sampled window) 2025-08-17T06:08:03Z 2026-09-21T16:01:47.904Z link
    evilhero/mylar metadata first observed — 2026-09-21T16:01:48.195Z link
    recent commit activity of evilhero/mylar observed (5 commits in sampled window) 2020-12-28T19:28:05Z 2026-09-21T16:01:48.876Z link
    automatic evaluation -> needs_review — 2026-09-21T16:01:57.004Z —
    evidence: successor_claim — 2026-09-21T16:01:57.004Z 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 → insufficient_data2026-09-21T14:37:31.042Z
    automatic evaluation → needs_review2026-09-21T16:01:57.004Z

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

    Snapshot taken at 2026-11-15T10:01:58.857Z (UTC).