Security and deployment remediation for issues #3-#11#21
Merged
Conversation
2 tasks
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
AlphaHorizon-AI
marked this pull request as ready for review
July 25, 2026 08:40
This was referenced Jul 25, 2026
Closed
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
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.
Summary
Implements the architecture-adjusted remediation for the security and deployment findings in issues #3?#11:
Contributor attribution
The straightforward contributor PRs #12?#17 and #19 were reviewed and merged directly. The findings in PRs #18 and #20 are accepted; this PR supplies the architecture-adjusted replacement where Shogun needs policy-based private-network support and a fully validated headless/container profile. Release notes credit @wstlima under Security contributors.
Root causes addressed
dangerouslySetInnerHTMLwithout first escaping HTML.Validation
npm cicompleted for both frontends.npm run audit:securitygates pass with only the documented, expiring GHSA-qwww-vcr4-c8h2 exception.The required container jobs pass clean image builds, Trivy scans, health/UI/auth smoke tests, non-root assertions, the Gensui frontend identity check, and the Mado Chromium launch.
Issues #9 and #11 will be closed after this PR is merged to main and the resulting main revision is verified.