Public ringsring index.
Public attribution sets, fully reproducible. Each ring is a deterministic hash of its members' public keys. Anyone can recompute the ring root and verify membership locally — no trust in this index required.
4 rings shown
- runtime/ 01
node-runtime/historic
Historic Node.js core authors and runtime contributors. Useful for runtime-level vulnerability disclosures where attribution must be provable but identity must remain private.
5 members·0 ghostsbafkreie0826365e67cd2629a1a59205fc458e35c7553f3188f3f6222beopen - kernel/ 02
linux-kernel/core
Subset of long-time Linux kernel maintainers. Demonstrates how a high-trust contributor set could expose anonymous attribution without revealing which maintainer signed.
4 members·0 ghostsbafkreia9ebd881ba683dd5e0b1810ca12d4f1fba752c699d0be9b0d56eopen - frontend/ 03
frontend/frameworks
A demonstration ring built from public maintainer keys across several frontend ecosystems. Shows how cross-project anonymous attribution would work in practice.
3 members·0 ghostsbafkreiea0f1d7815fda557303b536e93c6f7014b44722ea513d1eb9789open - privacy/ 04
privacy/engineering
A privacy-engineering attribution set: people whose public work touches anonymity, secure messaging, and adversarial threat models. Designed for sensitive disclosures.
3 members·0 ghostsbafkrei2d63014e34a828a4ec04839c751e37c094f73d50db7db9c9bdc6open
The rings shown here are derived from each member's public github.com/<user>.keys listing using a deterministic, reproducible derivation. Listed contributors have not endorsed gitghost. The rings are demonstration assemblies built from public material.