docs: add architecture analysis badge#2114
Open
karrolcia wants to merge 1 commit intoopenstatusHQ:mainfrom
Open
docs: add architecture analysis badge#2114karrolcia wants to merge 1 commit intoopenstatusHQ:mainfrom
karrolcia wants to merge 1 commit intoopenstatusHQ:mainfrom
Conversation
|
@karrolcia is attempting to deploy a commit to the OpenStatus Team on Vercel. A member of the Team first needs to authorize it. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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.
Hi team — I ran an architecture analysis of openstatus and wanted to share the result, plus offer a README badge if it's useful.
Analysis page: https://codesea.app/repo/openstatushq/openstatus
CodeSea maps how codebases work as systems — data flow stages, data models with concrete shapes, runtime behavior (feedback loops, control points), and hidden assumptions the code relies on but doesn't validate. The goal is making the architecture legible to new contributors without them having to read every file first.
The badge:
I matched your existing HTML badge format and added it at the end of your badge row. It's a static SVG from our CDN — no JS, no tracking, no runtime JavaScript.
If anything in the analysis is wrong or missing, I'd genuinely want to know — we're working on getting system analysis right, and openstatus is a clean example to learn from.
Happy to close this PR if the badge isn't a fit.