Harden repository foundation and trust scaffolding#2
Closed
Conversation
Member
Author
|
Connector merge actions were unavailable in this installation, so the hardening content was landed directly on |
mdheller
force-pushed
the
harden/foundation-content
branch
from
90fce9f to
deed40f
Compare
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.
This PR turns the empty placeholder hardening pass into a real repository-foundation baseline.
Included:
.editorconfig.github/CODEOWNERSCONTRIBUTING.mdSECURITY.mddocs/TRUST_ADDENDUM.md.github/workflows/validate.ymlIntent:
Follow-on work after merge:
socios-linux/lampstandsession_id,intent_id, workload identity, extractor receipts, route-policy invariants