Add the privacykey project status hub - #2
Merged
Conversation
status.json is the single source of truth for every privacykey repo's maintenance tier, and the badges, STATUS.md and org profile project list are generated from it by the shared workflow in privacykey/gh-workflows. Each account keeps its own hub, so a privacykey badge is served from a privacykey repo and no credential has to reach across the three identities. Badges are generated for public, listed repos only. The badges directory is browsable, so one file per repo would have published an index of the unreleased privacykey products. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The privacykey half of the portfolio status system. Opened from a fork — I don't have push on this repo.
gh-workflows#7 is merged and
v1carries the action, so this is ready to merge.Why the hub lives here rather than centrally
One shared hub would need a single credential able to read all three identities, stored in a public repo. Per-account, each token is scoped to its own owner — a leak costs one identity instead of three. It also means
privacytracker's status badge is served from a privacykey repo rather than a personal profile.The unified cross-account list still renders on the personal profile via
--aggregate, which needs no token: every hub is public and each already withholds its private repos.Needs a secret
STATUS_TOKEN— a fine-grained, read-only PAT scoped to privacykey only. Without it the build still runs; only the drift check is skipped, and it says so rather than reporting private repos as healthy.Tiers
🟢 Active 3 · 🚧 Building 6 · 🛡️ Maintained 5 · 📦 Parked 3 ·⚠️ Unmaintained 2 · 📁 Archived 1 — 8 of 20 listed publicly.
Seven things it flags, all verified:
website-privacykeyhas no README at all, and six private repositories have issues of their own — missing READMEs, empty git repositories, and failing CI. Details are in the run summary rather than here, since this repository is public.A correction
I earlier described this repo as a 9-byte stub with no SECURITY.md. That was stale scan data — it has carried the full community health set since 2026-08-07, so privacykey repos already inherit those files. It's graded 🛡️ Maintained here.
🤖 Generated with Claude Code