docs: add Ecosystem & porting status section to README#2
Open
nik2208 wants to merge 1 commit into
Open
Conversation
Adds a dedicated section to the README that tracks the parity status of all porting libraries (Go, Rust, Python, Dart server-side) and official client libraries (Angular, Flutter) against the reference implementation, each linking to its parity audit issue. Removes the now-redundant "Client libraries" row from the Features table (it's superseded by the new section).
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
1 participant
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.
Adds a new "Ecosystem & porting status" section to the README that tracks parity status of all porting libraries and client libraries against this reference implementation, each linking directly to its dedicated parity audit issue.
What's added
A dedicated section with two tables:
Server-side ports
awesome-go-authawesome-rust-authawesome-python-authawesome-dart-authClient libraries
ng-awesome-node-authawesome-node-auth-flutterWhat's removed
The single "Client libraries" row inside the Features table (which only mentioned Angular and Flutter and was easy to miss) — superseded by the new section, which covers both clients and server-side ports.
Why
There are now six parity-aligned repositories around the reference implementation. Without a central index, the relationships are easy to lose track of. The new section gives anyone landing on the main README an immediate map of:
What's not in scope
This is purely a docs change — no code, no version bump. The parity audits themselves are the work tracked separately in the six audit issues.