New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

Changelog

What's new at Socket?

November 13

New alert covering dual use tools

New “Dual-use functionality” alert that flags packages which are legitimate security research or testing tools, such as offensive security, penetration testing, or vulnerability research tooling. While not inherently malicious, their capabilities can be misused for unauthorized purposes, Organizations with strict security or compliance requirements may want to review them before allowing them in their environments.

November 12

New: Policy changes reach Socket Firewall in seconds

Hosted Socket Firewall now picks up changes to your security policy, license policy and triage rules within about 5 seconds. Before, the firewall kept using its cached decisions for 10 minutes, and up to an hour for package version listings. Now if you unblock a package, the developer’s next install goes through. Nothing to configure.

November 11

Socket Patch CLI 5.1.0

  • Expanded RubyGems support: Gems with native extensions are now rebuilt after patching, enabling support for nokogiri and other gems with native extensions. Hosted mode replaces already-installed gems while keeping your Gemfile declarations intact.
  • Recursive monorepo scanning:socket-patch scan now covers every project in a monorepo recursively, so you don’t have to run it on each workspace independently. Control this through socket.yml or options passed to the scan command.
  • Go workspaces are now supported.
  • Compatibility with existing patches: Packages you’ve already patched with tools like pnpm or patch-package are left alone unless you explicitly opt in to patching them.
  • Clearer scan results: Scans now list which advisories each patch fixes and which remain unresolved.
  • Faster patching on macOS: Applying patches is about 10x faster on large monorepos.

November 11

New: DNS-Aware Liveness Checks in Socket Registry Firewall

Socket Registry Firewall v2.17.0 adds /health/live, which checks DNS resolution across every nginx worker. Point your Kubernetes liveness probe at this endpoint so Kubernetes can restart the firewall when a worker fails its DNS check, helping prevent intermittent request failures that basic health checks can miss.

Version v2.18.0 also includes a request ID header on every outbound registry request, including metadata and cooldown lookups. If your outbound proxy routes traffic back through the firewall, use this header to identify the firewall’s own requests and avoid routing loops. The header defaults to X-Socket-Request-ID, and the firewall replaces any client-supplied value with its own.

Upgrade to v2.18.0 or later to get both improvements.

November 10

Fix: Fewer False Typosquat Alerts for Open VSX Extensions

Socket has reduced false typosquat alerts for Open VSX extensions that share common words with other listings, such as “Nifty REST Client” and “REST Client.”