Skip to content

Launch docs + Socket.dev supply-chain security#101

Open
yasserstudio wants to merge 2 commits into
mainfrom
chore/launch-docs-and-socket-security
Open

Launch docs + Socket.dev supply-chain security#101
yasserstudio wants to merge 2 commits into
mainfrom
chore/launch-docs-and-socket-security

Conversation

@yasserstudio

Copy link
Copy Markdown
Owner

Summary

Two independent, non-code follow-ups from the launch.

Launch status (docs)

  • Mark GMC as publicly launched on the docs home, the guide Status section, and the devlog intro, each linking the launch announcement.

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.yml
    • gatesocket ci as an enforceable status check (skips on fork PRs where the secret is withheld).
    • firewall — routes pnpm install through 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)

  • Install the Socket GitHub app on this repo.
  • Add a SOCKET_SECURITY_API_TOKEN repo secret (Socket dashboard → API token) for the gate job.
  • After a green run, mark gate a required status check in branch protection.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant