Repository navigation
Add encrypted recovery backups and security release checks - #73
Merged
Merged
Conversation
ChevCellios
enabled auto-merge (squash)
October 9, 2026 20:46
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 authenticated encrypted backups of committed Git history and selected application data, safe restore into a new directory, and a recovery runbook. Adds daily full-history secret scanning, container vulnerability checks, and isolated HTTP plus passive ZAP checks; Docker dependency updates are enabled.
Validation: 90 .NET tests and 23 Node tests passed, including a real Git bundle restore. Local secret scan found no leaks. Fresh container scan found no high/critical vulnerabilities; lower-severity findings remain in the complete report. Private HTTP probes passed. CI must validate the new passive scanner before merge.
Operational limits: the encrypted local backup is labelled local-preview. Railway rejected volume backup schedules because this workspace requires Pro; production volume export awaits approval for a temporary SSH key. Offsite storage and account MFA still need owner configuration.