Eclipse Namesake runs on your own machine — the client starts it, so there is no endpoint to ping.
Identity-collision similarity screen over a fixture registry snapshot; not a trademark opinion.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Alternatives to Eclipse Namesake
same job, measured the same wayPublic seal registry over fixture commitments: seal before the window, score at maturity.
Per-call voice continuity tokens over fixture call records; identifier-level detection only.
Prompt seal chain + Herald approval binding + incident traceability over fixture prompts only.
Screen names/IDs against Ukraine's NSDC State Sanctions Register (snapshot) via Apify.
Decision-evidence sealing + audit recompute over fixture decisions; local only.
Emission-time claim binder over fixture streams; unbound claims flagged in-message.
Simulated escrow-release witness over a fixture ledger; release only on counter-signed proof.
Fixture claim substantiation gate; pointer proves BOUND, not that it substantiates.
Eclipse Namesake — questions
Answers built from our own checks of this server.