Eclipse Safelist runs on your own machine — the client starts it, so there is no endpoint to ping.
Freshness-windowed signed allowlist feed over fixture entries; entries expire unless re-benched.
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 Safelist
same job, measured the same waySimulated escrow-release witness over a fixture ledger; release only on counter-signed proof.
Capture witness: content, headers + TLS cert sealed as one signed bundle; fixture captures only.
First-payment witnessed risk briefing over fixture sources with receipted acknowledgment.
Public seal registry over fixture commitments: seal before the window, score at maturity.
Fixture schedules freeze on verified witnessed change; simulator only, no payments executed.
Per-fact retrieval receipts over fixture source stores; not source truth, not answer faithfulness.
Eval-expiry clock over fixture Benchkit scorecards + fixture drift evidence; local stdio MCP only.
Signed death record triggers atomic cascade expiry of fixture instruments; local only.
Eclipse Safelist — questions
Answers built from our own checks of this server.