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

Changelog

What's new at Socket?

November 18

Fix: Nginx Security Updates in Socket Registry Firewall

Socket Registry Firewall v2.21.1 updates its Docker images with nine security fixes backported from nginx 1.31.9, addressing vulnerabilities in the firewall’s underlying web server.

Upgrade to Socket Registry Firewall v2.21.1 to apply these fixes to your deployment.

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.”

A similar name alone no longer triggers an alert. Socket now looks for further evidence of impersonation before flagging an extension, so you see fewer alerts to review and dismiss. Typosquat detection in other ecosystems is unchanged.

November 10

New: displayName in Socket threat feed API responses and webhooks

Threat Feed integrations can now show package names as they appear in their registries, making it easier to match a threat feed entry to the package you’re investigating. API responses and webhooks include a new displayName field, such as the crates.io spelling of a Cargo crate. The field can be null for Cargo, browser extension, and ClawHub entries, so integrations should treat it as optional.

November 10

Clearer Availability and Status for Socket Fix PRs

Socket Fix now disables the Open Socket Fix PR button for unsupported ecosystems, saving you from running a job that can’t upgrade the package. Hover over the button in the alert drawer to see the supported ecosystems: npm, Maven, NuGet, Go, Cargo, PyPI, and RubyGems.

When your organization hasn’t enabled Socket Fix pull requests, only Owners and Admins see the setup notice and Settings link. Other members won’t see the PR button until the organization enables the feature. Everyone can still see the Socket Fix card and socket fix CLI command on GHSA alerts.

Socket Fix now marks a job as failed when it makes no changes and produces no readable result, instead of showing “nothing to change.”

November 9

Fix: Org Alerts Now Honors Reachability Ignore Actions

Org Alerts now removes alerts that your policy sets to Ignore based on Tier 1 reachability results. For example, your policy may ignore an alert when the vulnerable code is unreachable. This fixes cases where an SCA scan’s Monitor action kept those alerts active when both scans covered the same branch, leaving you with unnecessary alerts to review. When reachability is unknown, the SCA scan’s action still applies.

November 8

New: Find PR Scans Faster with Search and Date Filters

The PRs tab on Scans now lets you search your organization’s PR scan history by repository, branch, PR number, title, or author. Searches ignore case and require at least two characters.

The new Filter → Created option replaces the Last 90 days dropdown. Choose a preset or specific dates to find PRs scanned or merged during that period. With no Created filter, the tab shows all available PR scan history.

On Repositories → Labels, new Security policy and License policy filters let you find labels where either policy is Enabled or Disabled.

Your searches and filters stay in the page URL, so you can bookmark a view or share it with your team.