Repository hygiene for Plumb: security policy, Dependabot, pinned Actions, lean dist - #1
Merged
Merged
Conversation
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.
Plumb scores this package 70 (Security 51.5) for four mechanical findings: no security policy, no dependency updater, Actions referenced by mutable tags, and dev files shipped in the Composer archive. This PR addresses all four without touching code: SECURITY.md with a private advisory route; weekly grouped Dependabot with a 7-day cooldown for Composer and Actions; workflow actions pinned to the current tags' commit SHAs; .gitattributes export-ignore for tests, CI and tooling; the docs workflow removed. Tag a release after merging so Plumb picks it up on the next scan.