Launch docs + Socket.dev supply-chain security#101
Open
yasserstudio wants to merge 2 commits into
Open
Conversation
Add a launched note to the docs home, the guide Status section, and the devlog intro, each linking the launch announcement.
- socket.yml: configure the Socket GitHub app (manifest-only triggers, ignore build output, pin high-signal alerts). - socket-security.yml: a `socket ci` policy gate plus a Socket Firewall job that routes installs through `sfw` to block known-malware versions at fetch time. - SECURITY.md: supported versions and private vulnerability reporting.
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
Two independent, non-code follow-ups from the launch.
Launch status (docs)
Supply-chain security (ci)
socket.yml— configure the Socket GitHub app: scan only on dependency-manifest changes, ignore build output, pin the high-signal alerts (malware, install scripts, typosquats, telemetry, native code)..github/workflows/socket-security.ymlgate—socket cias an enforceable status check (skips on fork PRs where the secret is withheld).firewall— routespnpm installthrough Socket Firewall (sfw) so known-malware versions are blocked at fetch time; runs on forks too. Cold install (no pnpm cache) so every fetch passes through the proxy.SECURITY.md— supported versions + private vulnerability reporting.No package code changes, so no changeset / release.
Follow-ups (manual)
SOCKET_SECURITY_API_TOKENrepo secret (Socket dashboard → API token) for thegatejob.gatea required status check in branch protection.