No entries match these filters. Clear filters
Expanded Java Coverage and More Accurate Reachability Results (2026-11-19)
Nov 19, 2026
·
issue 146
Socket adds Android AAR AAR After Action Review — a structured debrief process used to analyze what happened, why, and what to improve; cyber tools embed it to formalize incident retrospectives. analysis and Spring Boot auto-configuration tracing to its Java reachability engine︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Socket now analyzes Android libraries packaged as AARs and follows Spring Boot auto-configuration, Spring XML bean definitions, service loading, JPA and servlet descriptors, and calls from Java into Scala objects for full application reachability.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Vulnerabilities in libraries Socket could not analyze now show Unknown instead of an incorrect Unreachable result, with fallback to precomputed results when a vulnerability pattern does not match the package. Not checked yet Projects using multiple versions of a crate now get call stacks specific to each version rather than a shared stack. Not checked yet Reachability analysis performance and precision now improve for JavaScript, TypeScript, and Python projects, with particular gains for projects using PyTorch, and Go analysis also gains performance improvements. Not checked yet
Socket now analyzes Android libraries packaged as AARs and follows Spring Boot auto-configuration, Spring XML bean definitions, service loading, JPA and servlet descriptors, and calls from Java into Scala objects for full application reachability.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
3 more in Everything
Get Notified When Webhook Deliveries Fail (2026-11-17)
Nov 17, 2026
·
issue 146
Socket adds automatic failure notifications and health-status badges for outbound webhooks, with auto-disable after four days of continuous failures.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Re-enable a webhook after fixing its endpoint so previous failures no longer count toward automatic disabling.
📍 In the Socket dashboard, go to Settings › Webhooks, find the entry marked Deliveries failing , fix the endpoint URL or configuration, then set the webhook status back to Active.
Socket now emails organization Owners and Admins when every outbound webhook delivery has failed for 12 hours, including the scheduled disable date.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket now auto-disables an outbound webhook after four days of continuous delivery failures and sends a follow-up email. Not checked yet The webhooks table now shows Unhealthy and Deliveries failing status badges so teams can track affected endpoints and re-enable them after fixing the issue. Not checked yet
3 details in Everything
New: Malware Scanning for Terraform, HCL, and CMake (2026-11-17)
Nov 17, 2026
·
issue 146
Socket Basics 3.5.0: Reachability and Proxy Updates (2026-11-16)
Nov 16, 2026
·
issue 146
Socket 3.5.0 adds proxy support and fixes argument handling for full application reachability scans︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run a reachability scan covering both npm and PyPI ecosystems behind a corporate proxy, with a 90-second timeout and specific paths excluded.
copy
$ HTTPS_PROXY=https://proxy.corp.example:8080 socket scan --reach-ecosystems=npm,pypi --reach-analysis-timeout=90s --exclude-paths=test/ --exclude-paths=vendor/
Reachability scans now honour HTTPS_PROXY and NO_PROXY environment variables, enabling scans behind a corporate proxy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Pass repeated --exclude-paths flags to supply multiple path exclusions in reachability scans. Not checked yet Use --reach-analysis-timeout=90s syntax (equals-sign form) instead of the comma form for timeout arguments. Not checked yet socket_additional_params now preserves commas and quoted spaces within values, so options such as --reach-ecosystems=npm,pypi are passed through correctly. Not checked yet Full application reachability scans now require outbound access to api.socket.dev and storage.googleapis.com; Socket downloads the reachability engine directly instead of through npm. Not checked yet
+1 more
show less
Updates the reachability engine to Coana 15.15.0. Not checked yet
Reachability scans now honour HTTPS_PROXY and NO_PROXY environment variables, enabling scans behind a corporate proxy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
5 more in Everything
└──▷ BREAKING ON UPGRADE
! SOCKET_CLI_COANA_LAUNCHER no longer takes effect; Socket downloads the reachability engine directly and an npm mirror alone is no longer sufficient.! Older reachability engine versions released before this change cannot be used with --reach-version.! Full application reachability scans now require outbound access to api.socket.dev and storage.googleapis.com; existing setups that relied on an npm mirror must be updated.! The comma form --reach-analysis-timeout,90s is no longer correct; use --reach-analysis-timeout=90s instead.
Improved SPDX and CycloneDX SBOM Exports (2026-11-16)
Nov 16, 2026
·
issue 146
Socket adds supplier information and DEPENDS_ON relationships to SPDX SPDX An open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format. exports, and direct dependencies to CycloneDX CycloneDX An open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. exports︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Socket's SPDX exports now use DEPENDS_ON relationships (from project to dependencies) instead of DEPENDENCY_OF, and include supplier information or NOASSERTION when the publisher is unknown.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket's CycloneDX exports now include the project's direct dependencies. Not checked yet Platform-specific Ruby gems (such as nokogiri) now appear once per platform locked in Gemfile.lock, each with the registry version and a platform qualifier, so downstream tools can match them correctly. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
! If your integration reads DEPENDENCY_OF relationships from Socket's SPDX exports, update it to read DEPENDS_ON instead.! The first diff scan after this update will show affected platform-specific Ruby gems as removed and re-added once.
Socket adds a POST /v0/orgs/{ORG_SLUG}/full-scans API endpoint to upload multiple manifest files or CycloneDX CycloneDX An open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. SBOMs SBOMs A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. in a single full scan︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Upload two dependency manifests from different directories in one full scan to associate them with a repository.
copy
$ curl -X POST "https://api.socket.dev/v0/orgs/ORG_SLUG/full-scans?repo=REPO_SLUG" \
-H "Authorization: Bearer SOCKET_API_TOKEN" \
-F "[email protected]" \
-F "services/api/requirements.txt=@services/api/requirements.txt"
Upload a CycloneDX SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. as a named part so Socket maps it to the correct supported file type.
copy
$ POST /v0/orgs/ORG_SLUG/full-scans?repo=REPO_SLUG HTTP/1.1
Host: api.socket.dev
Authorization: Bearer SOCKET_API_TOKEN
Content-Type: multipart/form-data; boundary=socket-boundary
--socket-boundary
Content-Disposition: form-data; name="bom.cdx.json"; filename="bom.cdx.json"
Content-Type: application/json
SBOM_FILE_CONTENTS
--socket-boundary--
Create a full scan by uploading one or more manifest files (including CycloneDX SBOMs) via POST /v0/orgs/ORG_SLUG/full-scans?repo=REPO_SLUG using a multipart/form-data body, where each part's Content-Disposition Content-Disposition An HTTP response header that tells a browser whether to display a file inline or treat it as a download attachment, and under what filename — letting cyber tools control how retrieved files are handled or trigger forced downloads. field name sets the file's repository path; unmatched files are reported under unmatchedFiles in the response.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Authenticate the full-scans:create endpoint with a Bearer token Bearer token A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. scoped to full-scans:create. Not checked yet
2 details in Everything
Socket adds Full Application Reachability for Ruby/Bundler projects via the --reach flag, with tunable timeout, memory, and concurrency controls︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Compare baseline vs. reachability scan to see how many CVEs are actually exploitable in your Ruby app.
copy
$ socket scan create .
# note total CVE count, then:
socket scan create --reach .
Run reachability analysis offline on a large monorepo with extended timeout and memory, without uploading results.
copy
$ socket scan reach
# results saved to .socket.facts.json
Tune reachability analysis for a large Bundler project where the default 10-minute timeout and 8 GB memory limit are insufficient.
copy
$ socket scan create --reach \
--reach-analysis-timeout 20m \
--reach-analysis-memory-limit 32GB \
--reach-concurrency 4 \
.
Run reachability analysis on Ruby/Bundler projects with socket scan create --reach . to build a cross-dependency call graph and identify which CVEs have an exploitable call chain from app code to the vulnerable function.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Run reachability analysis locally without uploading results using socket scan reach, which saves output to .socket.facts.json. Not checked yet Tune large-project reachability scans with --reach-analysis-timeout (default 10m, accepts s, m, or h units), --reach-analysis-memory-limit (default 8GB, accepts MB or GB units, 16–32 GB recommended for large projects), and --reach-concurrency (maximum concurrent analysis runs, one per project or workspace). Not checked yet Pass --org <your-org-slug> on every socket scan create call, or run socket login once to set a default org slug. Not checked yet Set the API key via the SOCKET_SECURITY_API_TOKEN environment variable as an alternative to interactive login. Not checked yet
+2 more
show less
Filter scan results by reachability status in the Socket Dashboard, where the CLI also outputs a Noise% column calculated as ((Unreachable + NoSup + NoReach) / Total Vulns) × 100. Not checked yet Override unreachable CVEs with low business impact in the Socket Dashboard to suppress them from future scans. Not checked yet
Run reachability analysis on Ruby/Bundler projects with socket scan create --reach . to build a cross-dependency call graph and identify which CVEs have an exploitable call chain from app code to the vulnerable function.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Run reachability analysis locally without uploading results using socket scan reach, which saves output to .socket.facts.json. Not checked yet Tune large-project reachability scans with --reach-analysis-timeout (default 10m, accepts s, m, or h units), --reach-analysis-memory-limit (default 8GB, accepts MB or GB units, 16–32 GB recommended for large projects), and --reach-concurrency (maximum concurrent analysis runs, one per project or workspace). Not checked yet Filter scan results by reachability status in the Socket Dashboard, where the CLI also outputs a Noise% column calculated as ((Unreachable + NoSup + NoReach) / Total Vulns) × 100. Not checked yet Override unreachable CVEs with low business impact in the Socket Dashboard to suppress them from future scans. Not checked yet
2 more in Everything
Socket adds Full Application Reachability for Cargo projects via --reach, with local-only mode, performance tuning flags, and per-CVE triage in CLI and Dashboard.
New supported platform Run reachability analysis on Cargo projects with socket scan create --reach . to build a cross-dependency call graph and distinguish exploitable CVEs from noise, without compiling the project first. Not checked yet Run reachability analysis locally without uploading results using socket scan reach, which saves output to .socket.facts.json. Not checked yet Tune large Cargo workspace scans with --reach-analysis-timeout, --reach-analysis-memory-limit, and --reach-concurrency flags on socket scan create --reach. Not checked yet Authenticate without interactive login by setting the SOCKET_SECURITY_API_TOKEN environment variable. Not checked yet View per-CVE reachability status (Reach, Unreach, NoSup, NoReach, Skipped, Error) and a Noise% column in CLI output and in Socket Dashboard, and override unreachable CVEs to suppress them from future scans. Not checked yet
5 details in Everything
Socket: Adds --dynamic-sbom-inference so dotnet resolves the dependency graph per build, with reachability reported per build in .socket.facts.json files.
└──▷ TRY IT
Scan a .NET solution in CI and get a noise-reduced CVE list showing only exploitable paths, with the dependency graph resolved per build.
copy
$ socket scan create --reach --dynamic-sbom-inference .
Tune a large NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. monorepo scan that exceeds the default memory and timeout limits.
copy
$ socket scan create --reach \
--reach-analysis-timeout 20m \
--reach-analysis-memory-limit 32GB \
--reach-concurrency 4 \
.
Enable lock file generation in a .csproj so Socket can produce the most accurate dependency graph.
*.csproj
copy
<PropertyGroup>
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
</PropertyGroup>
Commit packages.lock.json for best accuracy, enabled by setting <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> in .csproj; Socket also reads *.csproj, packages.config, and *.nuspec directly. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! Delete .socket.facts.json before running socket scan create without --reach; if the file is present it is uploaded as an SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. carrying stale reachability results.
Socket: View per-ecosystem reachability results in a CLI summary table with Vulns, Reach, Unreach, NoSup, NoReach, Skipped, Error, Noise%, and Time columns.
└──▷ TRY IT
Establish a baseline CVE count, then run a reachability scan to filter out non-exploitable findings in a Go Modules project.
copy
$ socket scan create .
# note baseline CVE count, then:
socket scan create --reach .
Analyze a large Go monorepo locally without uploading, with extended timeout and higher memory and concurrency limits.
copy
$ socket scan create --reach \
--reach-analysis-timeout 30m \
--reach-analysis-memory-limit 32GB \
--reach-concurrency 4 .
Run reachability analysis offline and inspect results before deciding whether to upload.
└──▷ BREAKING ON UPGRADE
! Delete .socket.facts.json before running socket scan create without --reach; otherwise the file is uploaded as an SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. carrying stale reachability results.
Socket: Use --dynamic-sbom-inference on socket scan create to generate a .socket.facts.json per subproject for per-subproject reachability analysis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run a full reachability scan on a Gradle or Maven project to identify only the CVEs that are actually reachable from your application code.
copy
$ socket scan create --reach --dynamic-sbom-inference .
Analyze reachability locally without uploading a scan result — useful for sensitive codebases where you want to inspect .socket.facts.json before sharing.
copy
$ socket scan reach --dynamic-sbom-inference
Tune reachability analysis on a large multi-module project to avoid timeouts and memory exhaustion.
copy
$ socket scan create --reach --dynamic-sbom-inference --reach-analysis-timeout 20m --reach-analysis-memory-limit 32GB --reach-concurrency 4 .
Generate dependency manifests independently with socket manifest dynamic-sbom-inference, socket manifest gradle, socket manifest maven, or socket manifest scala before running a scan. Not checked yet Limit --dynamic-sbom-inference to JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. builds in a mixed repository by adding --dynamic-sbom-inference-ecosystems maven. Not checked yet Use CycloneDX CycloneDX An open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. SBOMs SBOMs A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. as an alternative manifest source by running socket cdxgen -t gradle -o socket-gradle.cdx.json --install-deps --lifecycle build (also -t maven and -t sbt). Not checked yet
3 details in Everything
└──▷ TRY IT
Identify which CVEs in a Poetry project are actually reachable from your application code, to cut triage noise before a release.
copy
$ socket scan create --reach --reach-analysis-memory-limit 32GB --reach-concurrency 4 .
Run reachability analysis on a uv project in CI without uploading results, then inspect the output file before promoting to a full scan.
Authenticate in a headless CI environment using an API key instead of interactive login.
copy
$ export SOCKET_SECURITY_API_TOKEN=sktsec_<your_key>
socket scan create --reach --org <your-org-slug> .
└──▷ BREAKING ON UPGRADE
! If .socket.facts.json is present and you run socket scan create without --reach, the file is uploaded as an SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. with stale reachability data — delete it first to avoid this.
└──▷ TRY IT
Compare total CVE count before and after enabling reachability to measure noise reduction in a large npm project.
copy
$ npm install
socket scan create .
# note baseline CVE count, then run with reachability:
socket scan create --reach --reach-analysis-memory-limit 32GB --reach-analysis-timeout 20m --reach-concurrency 4 .
Run reachability analysis locally on a pnpm workspace without uploading results, then inspect the output file before committing.
copy
$ pnpm install
socket scan reach
cat .socket.facts.json
Authenticate via API key in CI and run a reachability scan for a Yarn project without an interactive login.
copy
$ export SOCKET_SECURITY_API_TOKEN=sktsec_<your_key>
socket scan create --reach --org <your-org-slug> .
└──▷ BREAKING ON UPGRADE
! Delete .socket.facts.json before running socket scan create without --reach; if the file is present it is uploaded as an SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and carries stale reachability results.
Socket adds SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. export endpoints for CycloneDX 1.5 CycloneDX 1.5 An OWASP-maintained software bill-of-materials standard; version 1.5 added support for machine-learning model metadata and vulnerability disclosure reports, giving cyber tools richer supply-chain data to reason over. SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. , SPDX SPDX An open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format. SBOM, and OpenVEX OpenVEX An open specification and Go library, maintained by the OpenVEX community, for expressing VEX (Vulnerability Exploitability eXchange) statements in a standard JSON format so cyber tools can automate vulnerability triage. 0.2.0 via REST API︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pull a CycloneDX CycloneDX An open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. 1.5 SBOM from a completed scan to feed into Dependency-Track or an ASPM ASPM Application security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most. tool.
copy
$ export SOCKET_CLI_API_TOKEN=...
SCAN_ID=your-scan-id
curl -s -H "Authorization: Bearer $SOCKET_CLI_API_TOKEN" \
"https://api.socket.dev/v0/orgs/your-org/export/cdx/$SCAN_ID" > sbom.cdx.json
jq '{bomFormat, specVersion, components: (.components | length)}' sbom.cdx.json
Export an OpenVEX document from a full-reachability scan and suppress unreachable CVEs in a downstream vulnerability management tool.
copy
$ export SOCKET_CLI_API_TOKEN=...
SCAN_ID=your-scan-id
curl -s -H "Authorization: Bearer $SOCKET_CLI_API_TOKEN" \
"https://api.socket.dev/v0/orgs/your-org/export/openvex/$SCAN_ID" > socket.vex.json
jq '.statements | group_by(.status) | map({status: .[0].status, count: length})' socket.vex.json
Export a CycloneDX 1.5 SBOM for any scan via GET https://api.socket.dev/v0/orgs/your-org/export/cdx/<SCAN_ID>, returning all direct and transitive components with licenses and package URLs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Export an SPDX SBOM for any scan via GET https://api.socket.dev/v0/orgs/your-org/export/spdx/<SCAN_ID>, suited for procurement and federal or regulatory requests. Not checked yet Export an OpenVEX 0.2.0 document per scan via GET https://api.socket.dev/v0/orgs/your-org/export/openvex/<SCAN_ID>, carrying a affected, not_affected, or under_investigation status per CVE with reachability justification — importable into ASPM and vulnerability management tools to suppress unreachable findings. Not checked yet
3 details in Everything
Socket adds SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. Patches to apply code-level CVE fixes without changing package versions or lockfiles︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Find all reachable, patchable CVEs across your org's repos in the last 30 days to prioritize which packages to patch first.
copy
$ curl -s -H "Authorization: Bearer $SOCKET_CLI_API_TOKEN" "https://api.socket.dev/v0/orgs/your-org/historical/alerts?range=-30d&per_page=100&filters.cvePatchStatus=patch_available&filters.alertReachabilityType=reachable" | jq -r '[.items[]? | "\(.repoSlug) \(.artifact.name)@\(.artifact.version) \(.alert.props.cveId)"] | unique[]'
Scan a project for available patches and apply one by name without changing the manifest or lockfile.
copy
$ cd /path/to/your-app && npm ci && socket patch scan --json > patches.json && socket patch get minimist && npm test
Gate CI so it fails if patches were not applied — catching cases where the installed version no longer matches a saved patch.
copy
$ out=$(socket patch apply --json)
echo "$out" | jq -e '.status == "success" and (.patchesApplied + .alreadyPatched) > 0' >/dev/null \
|| { echo "Socket patch apply: $(echo "$out" | jq -c '{status, patchesApplied, alreadyPatched, failed}')"; exit 1; }
Automate patch reapplication after every npm install or npm ci by running socket patch setup --yes, which adds "postinstall": "socket patch apply --silent --ecosystems npm" to package.json.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Query reachable, patchable CVEs across all repos via the GET https://api.socket.dev/v0/orgs/your-org/historical/alerts endpoint using filters.cvePatchStatus=patch_available and filters.alertReachabilityType=reachable. Not checked yet Add --offline to socket patch apply to make it fail rather than fetch if a patch file is missing from .socket/blobs/. Not checked yet
3 details in Everything
Socket adds socket fix command to auto-remediate reachable CVEs and open fix pull requests in CI︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Audit what socket fix would change across all vulnerabilities before touching any files — useful for a first-pass review in a new project.
copy
$ socket fix --all --no-apply-fixes --output-file fixes.json
jq '.fixes | length' fixes.json
Schedule weekly automated fix PRs in CI, capped at 5 per run and restricted to package versions older than one week to reduce supply-chain risk.
.github/workflows/socket-fix.yml
copy
name: socket-fix
on:
schedule:
- cron: '0 6 * * 1'
permissions:
contents: write
pull-requests: write
jobs:
socket-fix:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
- run: npm ci
- name: Run Socket Fix
env:
SOCKET_CLI_API_TOKEN: ${{ secrets.SOCKET_CLI_API_TOKEN }}
SOCKET_CLI_GITHUB_TOKEN: ${{ secrets.SOCKET_FIX_GITHUB_TOKEN }}
run: npx --yes socket fix --pr-limit 5 --minimum-release-age 1w
Fix a single reachable CVE locally, verify tests still pass, then commit — keeping the blast radius to one advisory at a time.
copy
$ socket fix --id GHSA-xxxx-xxxx-xxxx
npm ci
npm test
git diff
Skip major-version bumps during automated fixing with --no-major-updates, or drop the flag for CVEs where a major upgrade is the only path.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Enable auto-merge on fix pull requests with --autopilot, which merges them automatically when all required checks pass. Not checked yet Socket adds a socket fix command that calculates the smallest set of upgrades to clear a vulnerability — including bumping a parent package when needed — and applies them to the manifest and lockfile; supports npm, pnpm, Yarn, uv, Poetry, Gradle, dotnet, Cargo, Bundler, and Maven. Not checked yet
3 details in Everything
Socket adds full application reachability analysis to resolve Potentially reachable CVE results down to Reachable or Unreachable using source-level scanning︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Scan an npm app with full reachability to collapse Potentially reachable CVEs into definitive Reachable/Unreachable verdicts, isolated on its own branch so it does not pollute the Alerts baseline.
copy
$ npm ci
socket scan create --org=your-org --repo="your-app" --branch="socket-reach" --reach --no-interactive .
Scan a large app in CI with raised memory and timeout limits to avoid out-of-memory out-of-memory An out-of-memory condition: a program requests more memory than the system or device can provide. The allocation fails or the operating system may stop the process. or timeout failures, running two parallel analysis workers.
copy
$ socket scan create --org=your-org --repo="your-app" --branch="socket-reach" --reach --no-interactive \
--reach-analysis-memory-limit 32GB \
--reach-analysis-timeout 30m \
--reach-concurrency 2 .
Run reachability in a CI pipeline using socketcli, constrained to the default branch only so pull requests stay on the faster standard scan.
copy
$ socketcli --target-path . --reach --reach-analysis-memory-limit 16GB --reach-analysis-timeout 30m
Skip analysis for a workspace that genuinely has no source files by adding --reach-continue-on-no-source-files to socket scan create. Not checked yet Enable dependency resolution for Gradle or sbt projects without a lock file by adding --dynamic-sbom-inference to socket scan create. Not checked yet Retain the intermediate facts file after a scan by passing --reach-retain-facts-file, which keeps .socket.facts.json in the scan directory for inspection instead of deleting it on success. Not checked yet Run reachability analysis in CI by adding --reach, --reach-analysis-memory-limit, and --reach-analysis-timeout to the socketcli command, using the same flags and value formats as the Socket CLI. Not checked yet Filter dashboard alerts by CVE Reachability in the scan report to compare Reachable, Unreachable, and Potentially reachable counts against the precomputed baseline. Not checked yet
+1 more
show less
Source code and dependency graphs are analyzed on the local machine — source is not uploaded to Socket's servers. Not checked yet
6 details in Everything
Socket adds three-tier reachability analysis to cut CVE noise, with a --reach flag for full call-path tracing from application code︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Count reachability verdicts across all CVE alerts in a scan to measure how much noise reachability analysis eliminates before triaging.
copy
$ export SOCKET_CLI_API_TOKEN=...
SCAN_ID=your-scan-id
curl -s -H "Authorization: Bearer $SOCKET_CLI_API_TOKEN" \
"https://api.socket.dev/v0/orgs/your-org/full-scans/$SCAN_ID" \
| jq -r '.alerts[]? | select(.type | test("CVE|cve")) | .reachability.head.results[0].type // "none"' \
| sort | uniq -c
Enable full application reachability — tracing call paths from your own code through direct and transitive dependencies — by adding --reach to a scan command.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Query reachability verdicts programmatically via GET https://api.socket.dev/v0/orgs/your-org/full-scans/$SCAN_ID, filtering CVE alerts by the top-level reachability field (not under props), with verdict values reachable, maybe_reachable, unreachable, pending, missing_support, direct_dependency, undeterminable_reachability, unknown, and error. Not checked yet Filter CVE alerts in the dashboard by the new CVE Reachability dimension, which accepts values including Unreachable and Direct dependency , to separate transitive noise from actionable findings. Not checked yet Socket now runs precomputed reachability on every scan with no setup required, checking whether transitive packages are imported and mapping call paths from direct dependencies down to vulnerable transitive packages. Not checked yet Python projects using requirements.txt now need uv.lockuv.lock A machine-generated lockfile produced by uv, Astral's Python package manager, that pins every dependency to an exact version and hash so builds are perfectly reproducible across machines. or poetry.lock committed for precomputed reachability to distinguish direct from transitive dependencies. Not checked yet
Enable full application reachability — tracing call paths from your own code through direct and transitive dependencies — by adding --reach to a scan command.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Query reachability verdicts programmatically via GET https://api.socket.dev/v0/orgs/your-org/full-scans/$SCAN_ID, filtering CVE alerts by the top-level reachability field (not under props), with verdict values reachable, maybe_reachable, unreachable, pending, missing_support, direct_dependency, undeterminable_reachability, unknown, and error. Not checked yet Filter CVE alerts in the dashboard by the new CVE Reachability dimension, which accepts values including Unreachable and Direct dependency , to separate transitive noise from actionable findings. Not checked yet Socket now runs precomputed reachability on every scan with no setup required, checking whether transitive packages are imported and mapping call paths from direct dependencies down to vulnerable transitive packages. Not checked yet
1 more in Everything
Socket Firewall adds a native Splunk HEC Splunk HEC An HTTP endpoint built into Splunk that accepts JSON-formatted log and event data pushed directly from applications or agents over HTTPS, letting cyber tools ship telemetry to Splunk without requiring a forwarder agent on the sending host. exporter configured via .env variables, with an explicit SPLUNK_SSL_VERIFY default of false.
New integration Configure the Splunk HEC HEC An HTTP API endpoint provided by Splunk that lets applications stream JSON-formatted events directly into a Splunk index without a forwarder agent, reducing pipeline complexity for log-shipping tools. exporter by setting SPLUNK_ENABLED, SPLUNK_HEC_URL, SPLUNK_HEC_TOKEN, SPLUNK_INDEX, SPLUNK_SOURCETYPE, and SPLUNK_SSL_VERIFY in the firewall's .env file — no webhook or forwarder needed. Not checked yet Set SPLUNK_SSL_VERIFY=true explicitly: the shipped default is false, meaning the HEC token is sent with no certificate check to whatever host answers at SPLUNK_HEC_URL. Not checked yet Query firewall events in Splunk using index=security sourcetype="socket:firewall" to surface blocked and allowed package installs with purl, block_reason, and request_id fields. Not checked yet
3 details in Everything
Socket Firewall adds a webhook to POST package decisions as JSON or NDJSON NDJSON A text format where each line is a self-contained JSON object, making it easy to stream, append, and parse large datasets record-by-record without loading the whole file into memory. to any HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. endpoint, including SIEMs SIEMs Security Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point. and ticketing systems︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Forward all firewall decision types to a SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. or log collector so your SIEM can show allowed installs, warnings, and blocks, not just blocks alone.
.env
copy
WEBHOOK_ENABLED=true
WEBHOOK_URL=https://collector.example.com/socket-firewall
WEBHOOK_AUTH_HEADER=Bearer your_receiver_token
WEBHOOK_ON_BLOCK=true
WEBHOOK_ON_WARN=true
WEBHOOK_ON_IGNORE=true
WEBHOOK_ON_MONITOR=true
WEBHOOK_SSL_VERIFY=true
Apply the new .env webhook settings — environment variables are only read at container startup, so a force-recreate is required.
copy
$ docker compose up -d --force-recreate
Enable webhook delivery of firewall decisions by setting WEBHOOK_ENABLED=true and WEBHOOK_URL in the firewall's .env file, with an optional WEBHOOK_AUTH_HEADER sent as the Authorization header.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Control which decision types are forwarded by toggling WEBHOOK_ON_BLOCK, WEBHOOK_ON_WARN, WEBHOOK_ON_IGNORE, and WEBHOOK_ON_MONITOR independently. Not checked yet Enable batched NDJSON delivery (one event per line, application/x-ndjson) with WEBHOOK_BATCH_ENABLED=true; WEBHOOK_BATCH_SIZE controls the batch size in bytes. Not checked yet Disable TLS verification for local testing by setting WEBHOOK_SSL_VERIFY=false. Not checked yet Route blocked-package events to Microsoft Sentinel or Defender XDR XDR Extended detection and response, combining signals and investigation across endpoints, networks, identities or cloud services. It helps analysts connect activity that separate tools might miss. by pointing WEBHOOK_URL at an Azure Function or Logic App that writes to a custom Log Analytics table or forwards to an Event Hub. Not checked yet
+2 more
show less
Route firewall decisions to syslog-only SIEMs by pointing the webhook at Logstash or another forwarder that emits syslog. Not checked yet Route firewall decisions to ticketing systems such as Jira or ServiceNow by pointing the webhook at an automation tool and filtering on decision = blocked. Not checked yet
7 details in Everything
Socket adds a firewall decision-event data page documenting JSON event fields, container log settings, and output routing to Splunk, webhooks, or stdout︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Capture every firewall decision including clean allows to stdout so you can ship the full install-decision stream to your SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. .
copy
$ # Add to .env
SOCKET_IGNORE_LOG_LEVEL=warn
# Recreate the container and tail decision events
docker compose up -d --force-recreate
docker compose logs socket-firewall | grep SOCKET_DECISION
Route firewall decision events to Splunk HEC Splunk HEC An HTTP endpoint built into Splunk that accepts JSON-formatted log and event data pushed directly from applications or agents over HTTPS, letting cyber tools ship telemetry to Splunk without requiring a forwarder agent on the sending host. , a webhook (Sentinel, Defender XDR XDR Extended detection and response, combining signals and investigation across endpoints, networks, identities or cloud services. It helps analysts connect activity that separate tools might miss. , Elastic, ticketing workflows), or container stdout by setting environment variables on the container.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Every firewall decision event is JSON with event_type: firewall_package_encountered and fields including timestamp, client_ip, registryFqdn, repo, purl, artifact_purl, action, decision, block_reason, warn_reason, blocked_alerts, request_id, and cached. Not checked yet Log every firewall decision — including clean allows hidden by default — by adding SOCKET_IGNORE_LOG_LEVEL=warn to .env and recreating the container, then filtering with docker compose logs socket-firewall | grep SOCKET_DECISION. Not checked yet Filter event_category: "proactive" events out of install-block counts when metadata filtering is on, as each version listing generates one proactive event per version up to max_versions. Not checked yet Use decision rather than action to determine what the client actually received, since some allowed downloads carry action: error (for example under the recently_published_enabled_ecosystems Cooldown setting). Not checked yet
+2 more
show less
Detect the real requester behind a load balancer by setting client_ip.header and client_ip.trusted_proxies in socket.yml. Not checked yet Dedupe PyPI events on purl plus client_ip, since pip downloads a .whl.metadata file and then the wheel, producing two events with the same purl and different source_path. Not checked yet
7 details in Everything
Socket adds CI/CD integration guide for the SFW registry, routing npm and pip installs through a firewall proxy that blocks packages at install time︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Wire a GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. job to block malicious packages at install time for both npm and pip without changing your existing install steps.
.github/workflows/build.yml
copy
jobs:
build:
runs-on: ubuntu-latest
env:
NPM_CONFIG_REGISTRY: https://sfw.example.com/npm/
PIP_INDEX_URL: https://sfw.example.com/pypi/simple/
steps:
- uses: actions/checkout@v4
- name: Install firewall CA
run: |
printf "%s\n" "$SFW_CA_PEM" | sudo tee /usr/local/share/ca-certificates/sfw-ca.crt > /dev/null
sudo update-ca-certificates
echo "NODE_EXTRA_CA_CERTS=/usr/local/share/ca-certificates/sfw-ca.crt" >> "$GITHUB_ENV"
echo "PIP_CERT=/etc/ssl/certs/ca-certificates.crt" >> "$GITHUB_ENV"
env:
SFW_CA_PEM: ${{ secrets.SFW_CA_PEM }}
- run: npm ci
Bake SFW registry and CA trust into a custom CI container image so every pipeline that uses it is protected with no per-job configuration.
Dockerfile
copy
COPY sfw-ca.pem /usr/local/share/ca-certificates/sfw-ca.crt
RUN update-ca-certificates
ENV NODE_EXTRA_CA_CERTS=/usr/local/share/ca-certificates/sfw-ca.crt \
PIP_CERT=/etc/ssl/certs/ca-certificates.crt \
NPM_CONFIG_REGISTRY=https://sfw.example.com/npm/ \
PIP_INDEX_URL=https://sfw.example.com/pypi/simple/
Route npm, pnpm, and Yarn 1 installs through the SFW firewall proxy by setting NPM_CONFIG_REGISTRY to https://sfw.example.com/npm/ in CI environment variables.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Route pip installs through the SFW firewall proxy by setting PIP_INDEX_URL to https://sfw.example.com/pypi/simple/ in CI environment variables. Not checked yet Trust the firewall's CA certificate for Node.js by pointing NODE_EXTRA_CA_CERTS at the CA file — this adds to Node's existing trust list rather than replacing it. Not checked yet Trust the firewall's CA certificate for pip by pointing PIP_CERT at a CA bundle that includes the firewall CA — note that PIP_CERT replaces pip's entire bundle, so point it at the system bundle (/etc/ssl/certs/ca-certificates.crt) after adding the firewall CA via update-ca-certificates. Not checked yet Bake registry and CA settings into a container image using ENV NPM_CONFIG_REGISTRY, PIP_INDEX_URL, NODE_EXTRA_CA_CERTS, and PIP_CERT so no per-pipeline changes are needed. Not checked yet
+1 more
show less
Verify the firewall integration by adding lodahs to a test branch and confirming the build fails with E403 ... Blocked by Security Policy. Not checked yet
6 details in Everything
Socket Firewall adds domain-based DNS override routing so clients reach the firewall without any package manager reconfiguration︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Switch Socket Firewall from path routing to domain-based routing so npm and pip clients need no reconfiguration — back up the existing config first.
copy
$ cp socket.yml socket.yml.path-routing
Domain-based routing config that makes the firewall intercept npm and PyPI traffic transparently using real registry hostnames.
socket.yml
copy
socket:
api_url: https://api.socket.dev
fail_open: true
ports:
http: 8080
https: 8443
registries:
npm:
domains: [registry.npmjs.org]
upstream: https://registry.npmjs.org
pypi:
domains: [pypi.org, files.pythonhosted.org]
upstream: https://pypi.org
Validate that a single test machine is fully covered before org-wide rollout — no real registry addresses should appear.
copy
$ getent ahosts registry.npmjs.org
Configure domain-based routing in socket.yml using registries[].domains and registries[].upstream keys so the firewall answers directly for registry.npmjs.org, pypi.org, and files.pythonhosted.org without requiring client-side package manager changes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Generate a TLS certificate covering all registry hostnames via -addext 'subjectAltName=DNS:registry.npmjs.org,DNS:pypi.org,DNS:files.pythonhosted.org' so intercepted HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. connections succeed without client reconfiguration. Not checked yet Prove out DNS override on a single machine by adding firewall IP entries for registry.npmjs.org, pypi.org, and files.pythonhosted.org in /etc/hosts before corporate rollout. Not checked yet Track client coverage by matching the client_ip field in firewall decision events against MDM MDM Mobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. , DHCP, or VPN VPN A virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. records. Not checked yet
4 details in Everything
Socket Firewall adds metadata filtering to remove blocked package versions from registry listings before the client resolves them︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Turn on metadata filtering for a fresh firewall deployment so blocked versions are pruned from registry responses before npm resolves a semver range.
.env
copy
METADATA_FILTERING_ENABLED=true
Verify that a blocked version is absent from the firewall's metadata listing before testing an install.
copy
$ diff <(curl -s https://registry.npmjs.org/is-odd | jq -r '.versions | keys[]') \
<(curl -sk https://sfw.example.com/npm/is-odd | jq -r '.versions | keys[]')
Enable metadata filtering by setting METADATA_FILTERING_ENABLED=true in .env, so the firewall strips blocked versions from package metadata before the client resolves a version range.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure metadata filtering via a top-level metadata_filtering: block in socket.yml, with settings enabled, filter_warn, max_versions, include_unchecked_versions, and cache_ttl. Not checked yet Control whether versions with a Warn action are hidden from listings with filter_warn (default false); set to true to also remove warned versions. Not checked yet Tune how many versions per package are checked with max_versions (default 100 newest versions) to cover teams installing older releases of active packages. Not checked yet Block versions Socket has not yet scanned from both listings and downloads by setting socket.fail_open_unscanned: false or SOCKET_FAIL_OPEN_UNSCANNED=false. Not checked yet
+2 more
show less
Metadata filtering now covers npm, Go, RubyGems, Cargo, Conda, OpenVSX, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , PyPI, and Maven, each filtered at the appropriate per-version or per-file granularity. Not checked yet Filter activity is logged as decision events with event_category: "proactive" and decision: "blocked" so SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. pipelines can distinguish proactive listing checks from real install blocks. Not checked yet
7 details in Everything
Socket Firewall adds Redis-backed distributed verdict caching to share allow/warn/block decisions across instances and survive restarts︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Add Redis to a Socket Firewall deployment so verdicts survive restarts and are shared across all firewall instances.
.env
copy
REDIS_ENABLED=true
REDIS_HOST=redis
REDIS_PORT=6379
REDIS_PASSWORD=change_me_to_a_long_random_string
Connect a Socket Firewall instance to a managed Redis service (ElastiCache, Azure Cache for Redis) with mutual TLS mutual TLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. .
.env
copy
REDIS_ENABLED=true
REDIS_HOST=redis.example.com
REDIS_PORT=6379
REDIS_PASSWORD=change_me_to_a_long_random_string
REDIS_SSL=true
REDIS_SSL_VERIFY=true
REDIS_SSL_CA_CERT=/etc/redis-tls/ca.pem
REDIS_SSL_CLIENT_CERT=/etc/redis-tls/client.pem
REDIS_SSL_CLIENT_KEY=/etc/redis-tls/client-key.pem
REDIS_SSL_SERVER_NAME=redis.example.com
Force fresh verdicts after a policy change or waiver when Redis persistence is active, since a firewall restart alone no longer clears the cache.
copy
$ rc() { docker compose exec -T redis redis-cli --no-auth-warning -a "$(grep '^REDIS_PASSWORD=' .env | cut -d= -f2-)" "$@"; }
rc FLUSHDB
Enable Redis verdict caching across firewall instances by setting REDIS_ENABLED=true, REDIS_HOST, REDIS_PORT, and REDIS_PASSWORD in .env.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Control cache freshness with cache.ttl (default 600 s for fresh verdicts) and redis.ttl (default 86400 s before Redis removes the entry). Not checked yet Configure the re-check behavior for expired allow verdicts with cache.confirm_allow_mode (default wait). Not checked yet Enable TLS for managed Redis services (such as ElastiCache or Azure Cache for Redis) with REDIS_SSL=true and REDIS_SSL_VERIFY=true in .env, with optional REDIS_SSL_CA_CERT, REDIS_SSL_CLIENT_CERT, REDIS_SSL_CLIENT_KEY, and REDIS_SSL_SERVER_NAME for private CA or mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. setups. Not checked yet Configure Redis connection and TLS settings alternatively under a redis: block in socket.yml using ssl_ca_cert, ssl_client_cert, ssl_client_key, and ssl_server_name. Not checked yet
+2 more
show less
Cache holds verdicts only (allow, warn, block) — package bytes always stream from the upstream registry. Not checked yet Share verdicts across multiple firewall instances by pointing all of them at the same REDIS_HOST. Not checked yet
7 details in Everything
└──▷ BREAKING ON UPGRADE
! With Redis enabled, restarting the firewall no longer clears verdicts — run FLUSHDB via redis-cli to force fresh verdicts after a policy change or waiver.
Socket adds a policy configuration guide for Socket Firewall, covering both the new Policies system and the legacy Security Policy API with verdict verification.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Check what Socket would decide for specific package versions before applying or testing a firewall policy change.
copy
$ curl -s -X POST "https://api.socket.dev/v0/purl?alerts=true" \
-H "Authorization: Bearer $SOCKET_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"components":[{"purl":"pkg:npm/[email protected]"},{"purl":"pkg:npm/[email protected]"}]}' \
| jq -c 'select(.name!=null)|{p:"\(.name)@\(.version)",actions:([.alerts[]?|{t:.type,a:.action}]|unique)}'
Dry-run a package deny rule against the Default policy before creating it, to confirm the payload is valid.
copy
$ ORG=your-org
DEFAULT_ID=$(curl -s -H "Authorization: Bearer $SOCKET_API_KEY" \
"https://api.socket.dev/v0/orgs/$ORG/alert-policies" \
| jq -r '.. | objects | select(.apply_method? == "unlabeled_repos") | .id' | head -1)
# Dry-run first, then create
for q in "?dry_run=true" ""; do
curl -s -X POST \
-H "Authorization: Bearer $SOCKET_API_KEY" \
-H 'Content-Type: application/json' \
"https://api.socket.dev/v0/orgs/$ORG/alert-policies/$DEFAULT_ID/rules$q" \
-d '{"name":"Deny is-odd 3.0.1",
"vigil_selector":{"artifact.type":"npm","artifact.name":"is-odd","artifact.version":"3.0.1"},
"action":"error",
"note":"Deny list: superseded internally"}'
echo
done
Prevent the firewall from allowing packages Socket has not yet scanned, by disabling fail-open behavior in the firewall config.
socket.yml
copy
socket.fail_open_unscanned: false
Verify what Socket would decide for a package using POST https://api.socket.dev/v0/purl?alerts=true before confirming a policy change. Not checked yet Adds the new Policies system: manage policies via GET/POST/PUT/DELETE https://api.socket.dev/v0/orgs/{org}/alert-policies and per-policy rules via https://api.socket.dev/v0/orgs/{org}/alert-policies/{id}/rules, using scopes alert-policy:list, alert-policy:create, alert-policy:update, and alert-policy:delete on a separate admin token; dry-run a new deny rule by appending ?dry_run=true to the POST https://api.socket.dev/v0/orgs/{org}/alert-policies/{id}/rules call; and choose a baseline preset (Balanced or Comprehensive ) in Policies → Default , layering custom Vigil-selector rules above it, where the first match wins. Not checked yet Under the legacy Security Policy system, set per-alert-type actions via POST https://api.socket.dev/v0/orgs/{org}/settings/security-policy with a policyRules body (GET returns the same data under the key securityPolicyRules), and deny or allow a specific package version via POST https://api.socket.dev/v0/orgs/{org}/triage/alerts with state: block or state: ignore. Not checked yet Socket Firewall policy now supports four actions — error (block, 403), warn (allow, adding an X-Socket-Warn-Reason header), monitor (allow, recorded silently), and ignore (allow, no record) — applied org-wide without a firewall restart, with blocked (403) responses now also carrying an x-socket-block-reason header. Not checked yet Cache verdicts survive restarts when Redis is used; clear them by running FLUSHDB against the Redis instance, or restart the container for in-memory caches — the TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. is controlled by cache.ttl (default 600 s). Not checked yet
Verify what Socket would decide for a package using POST https://api.socket.dev/v0/purl?alerts=true before confirming a policy change. Not checked yet Adds the new Policies system: manage policies via GET/POST/PUT/DELETE https://api.socket.dev/v0/orgs/{org}/alert-policies and per-policy rules via https://api.socket.dev/v0/orgs/{org}/alert-policies/{id}/rules, using scopes alert-policy:list, alert-policy:create, alert-policy:update, and alert-policy:delete on a separate admin token; dry-run a new deny rule by appending ?dry_run=true to the POST https://api.socket.dev/v0/orgs/{org}/alert-policies/{id}/rules call; and choose a baseline preset (Balanced or Comprehensive ) in Policies → Default , layering custom Vigil-selector rules above it, where the first match wins. Not checked yet Socket Firewall policy now supports four actions — error (block, 403), warn (allow, adding an X-Socket-Warn-Reason header), monitor (allow, recorded silently), and ignore (allow, no record) — applied org-wide without a firewall restart, with blocked (403) responses now also carrying an x-socket-block-reason header. Not checked yet Cache verdicts survive restarts when Redis is used; clear them by running FLUSHDB against the Redis instance, or restart the container for in-memory caches — the TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. is controlled by cache.ttl (default 600 s). Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! Once an organization migrates to Policies, writes to the legacy security-policy and triage endpoints are rejected: POST returns 409, PUT and DELETE return 405. Reads still work but show a frozen copy.
Socket: Set a Recently Published Alert Threshold in Dashboard → Settings → Alerts → Scans to auto-block new package versions until they age past it.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Allow recent npm packages through the cooldown while keeping other ecosystems blocked — add this to your existing socket.yml and recreate the container.
socket.yml
copy
socket:
api_url: https://api.socket.dev
fail_open: true
recently_published_enabled_ecosystems:
- npm
Programmatically grant a one-version waiver for a specific package in the new Policies system, so a pinned release clears the firewall's 403 without disabling the cooldown for other versions.
copy
$ curl -s -X POST -H "Authorization: Bearer $SOCKET_API_KEY" -H 'Content-Type: application/json' \
"https://api.socket.dev/v0/orgs/$ORG/alert-policies/$DEFAULT_ID/rules" \
-d '{"name":"Cooldown waiver rollup 4.25.0",
"vigil_selector":{"artifact.type":"npm","artifact.name":"rollup","artifact.version":"4.25.0",
"finding.alertType":"recentlyPublished"},
"action":"ignore",
"note":"Waiver TICKET-123, approved by NAME"}'
Confirm Socket flags a freshly published package with a recentlyPublished alert before testing it through the firewall.
copy
$ curl -s -X POST "https://api.socket.dev/v0/purl?alerts=true" \
-H "Authorization: Bearer $SOCKET_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"components":[{"purl":"pkg:npm/rollup@4.25.0"}]}' \
| jq -c 'select(.name!=null)|[.alerts[]?|select(.type=="recentlyPublished")|.action]'
Allow recent versions through for selected package ecosystems by adding recently_published_enabled_ecosystems to socket.yml; listed ecosystems receive a 200 with x-socket-block-reason suppressed while unlisted ones stay blocked. Not checked yet Script cooldown waivers for the new Policies system via POST https://api.socket.dev/v0/orgs/{org}/alert-policies/{id}/rules or POST https://api.socket.dev/v0/orgs/{org}/alerts/resolutions, using tokens scoped to alert-policy:list, alert-policy:create, or alert-resolution:create. Not checked yet Count cooldown blocks in a SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. on the decision field (not action) in logs, webhooks, and Splunk, because ecosystems allowed via recently_published_enabled_ecosystems log decision: allowed with action: error. Not checked yet
3 details in Everything
Socket adds Registry Mode firewall documentation covering setup of a Docker-based package-intercept proxy for npm and PyPI︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Bootstrap the firewall for npm and PyPI in a strict posture so any Socket API outage blocks installs rather than allowing them through.
~/socket-fw/socket.yml
copy
socket:
api_url: https://api.socket.dev
fail_open: false
ports:
http: 8080
https: 8443
cache:
ttl: 600
path_routing:
enabled: true
domain: sfw.example.com
rewrite_scheme: https
routes:
- path: /npm
upstream: https://registry.npmjs.org
registry: npm
- path: /pypi
upstream: https://pypi.org
registry: pypi
Set required environment variables, including the firewall-specific API token, before starting the container.
~/socket-fw/.env
copy
SOCKET_SECURITY_API_TOKEN=your_api_key_here
SOCKET_FAIL_OPEN=true
SOCKET_IGNORE_LOG_LEVEL=warn
Start the firewall and confirm it can reach Socket and load verdicts before routing real traffic through it.
copy
$ docker compose up -d
for i in $(seq 1 30); do curl -sk https://sfw.example.com/health && break; sleep 2; done
docker compose logs socket-firewall | grep 'Resolved org slug from API'
Run Socket Firewall in Registry Mode using socketdev/socket-registry-firewall:latest as a Docker container that proxies npm and PyPI requests and returns HTTP 403 for blocked packages.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure per-ecosystem routes in socket.yml using path_routing.routes entries, each with a path, upstream registry URL, and registry type (e.g. npm or pypi). Not checked yet Set fail_open: true or fail_open: false in socket.yml to control whether installs are allowed or denied when the Socket API is unreachable. Not checked yet Set path_routing.use_incoming_domain: true in socket.yml so rewritten download URLs preserve the client's host and port when the firewall is not published on port 443. Not checked yet Supply the API token via the SOCKET_SECURITY_API_TOKEN environment variable (requires packages:list and entitlements:list scopes); this is distinct from the variable used by the Socket CLI or CI integrations. Not checked yet
+2 more
show less
Control verdict log verbosity with the SOCKET_IGNORE_LOG_LEVEL environment variable (e.g. warn to suppress clean-package log entries). Not checked yet Set cache.ttl in socket.yml to configure how long (in seconds) package verdicts are cached locally. Not checked yet
7 details in Everything
Socket adds a Firewall Registry Mode container that intercepts package manager traffic and blocks malicious packages before they reach the machine︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Block malicious packages — including transitive dependencies — at download time by routing package manager traffic through the firewall. Not checked yet Hold back newly published package versions for a configurable number of days with Cooldown mode. Not checked yet Control what is blocked, warned, or allowed per-package via policy configuration. Not checked yet Hide blocked package versions from resolution so installs fall back to an allowed version via metadata filtering. Not checked yet Route traffic through the firewall with no client-side changes using DNS override. Not checked yet
+3 more
show less
(new) Adds Configure registry: dev and Configure registry: CI/CD guides for pointing developer machines and CI/CD pipelines/Docker builds at the firewall. Not checked yet (new) Streams firewall decisions to any HTTP endpoint via webhook configuration, or to Splunk via the Splunk config integration. Not checked yet Authenticate to the firewall using a Socket API token with packages:list and entitlements:list scopes, obtained from Settings → API Tokens. Not checked yet
8 details in Everything
Socket reachability analysis now handles multiple versions of the same vulnerable package without raising an analysis error, and no longer reuses prior scan splits when analysis splitting is on.
Updated supported platform Reachability analysis no longer reuses how the previous scan of the same repository and branch split up its vulnerabilities when analysis splitting is enabled. Not checked yet Reachability analysis no longer reports an analysis error for a vulnerability when a project's dependency tree holds multiple versions of the vulnerable package and a vulnerability pattern fails to apply to only one of them. Not checked yet
2 details in Everything
New alert covering dual use tools (2026-11-13)
Nov 13, 2026
·
issue 141
New: Policy changes reach Socket Firewall in seconds (2026-11-12)
Nov 12, 2026
·
issue 141
Socket Firewall now picks up security policy, license policy, and triage rule changes within about 5 seconds instead of up to an hour︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Socket Patch CLI 5.1.0 (2026-11-11)
Nov 11, 2026
·
issue 141
Socket Patch CLI 5.1.0 adds recursive monorepo scanning, Go workspace support, and native-extension RubyGems rebuilding︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Scan an entire monorepo recursively from the root rather than running socket-patch per workspace.
Socket Patch CLI now supports Go workspaces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket Patch CLI now rebuilds gems with native extensions after patching, enabling support for nokogiri and other native-extension gems; hosted mode replaces already-installed gems while keeping Gemfile declarations intact. Not checked yet
Socket Patch CLI now supports Go workspaces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
New: DNS-Aware Liveness Checks in Socket Registry Firewall (2026-11-11)
Nov 11, 2026
·
issue 141
Socket Registry Firewall adds a DNS-aware liveness endpoint and a per-request ID header to aid Kubernetes health checks and loop detection︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Wire the new DNS-aware endpoint into a Kubernetes liveness probe so the pod restarts automatically when any nginx worker loses DNS resolution.
yaml
copy
livenessProbe:
httpGet:
path: /health/live
port: 80
initialDelaySeconds: 10
periodSeconds: 15
Point Kubernetes liveness probes at the new GET /health/live endpoint, which checks DNS resolution across every nginx worker so Kubernetes can restart the firewall when a worker fails its DNS check.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Fix: Fewer False Typosquat Alerts for Open VSX Extensions (2026-11-10)
Nov 10, 2026
·
issue 141
New: displayName in Socket threat feed API responses and webhooks (2026-11-10)
Nov 10, 2026
·
issue 141
Socket's Threat Feed API responses and webhooks now include a displayName field showing registry-native package names︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
When consuming the Threat Feed API, read displayName to get the exact crates.io (or other registry) spelling of a flagged package, then cross-reference it directly in your registry or dependency manifest.
copy
$ curl -s -H 'Authorization: Bearer <token>' 'https://api.socket.dev/v0/threat-feed' | jq '.[] | {displayName: .displayName, name: .name, severity: .severity}'
Clearer Availability and Status for Socket Fix PRs (2026-11-10)
Nov 10, 2026
·
issue 141
Socket adds clearer availability signals for Fix PRs, disabling the button for unsupported ecosystems and surfacing role-based setup notices︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Socket Fix now disables the Open Socket Fix PR button for unsupported ecosystems — npm, Maven, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Go, Cargo, PyPI, and RubyGems are supported — so members can see at a glance whether an upgrade job can run before clicking.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Owners and Admins now see a setup notice and Settings link when Socket Fix pull requests are not yet enabled for the organization; other members see no PR button until the feature is turned on. Not checked yet
Socket Fix now disables the Open Socket Fix PR button for unsupported ecosystems — npm, Maven, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Go, Cargo, PyPI, and RubyGems are supported — so members can see at a glance whether an upgrade job can run before clicking.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Socket Firewall adds VS Code, Cursor, and Antigravity extension marketplace routing to block malicious IDE extensions︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Enforce extension marketplace filtering for all VS Code users on managed Linux machines via policy file.
/etc/vscode/policy.json
copy
{
"ExtensionGalleryServiceUrl": "https://sfw.your_company.com:8443/vscode/vscode/gallery"
}
Enforce extension marketplace filtering for a single developer's VS Code desktop install without a managed policy.
settings.json
copy
{
"extensions.gallery.serviceUrl": "https://sfw.your_company.com:8443/vscode/vscode/gallery"
}
Route VS Code extension installs through the Socket Firewall by setting "extensions.gallery.serviceUrl" in settings.json to https://sfw.your_company.com:8443/vscode/vscode/gallery, or deploy the ExtensionGalleryServiceUrl policy via Group Policy, Intune, a macOS configuration profile, or /etc/vscode/policy.json on Linux for managed devices.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Route Cursor extension installs through the Socket Firewall using the openvsx route at https://sfw.your_company.com:8443/openvsx/vscode/gallery, configurable via Settings → VS Code Settings → marketplace service URL, or via Cursor's macOS profile or Windows Group Policy for managed fleets. Not checked yet Route Antigravity IDE extension installs through the Socket Firewall by setting the Gallery URL to https://sfw.your_company.com:8443/openvsx/vscode/gallery and the Item URL to https://sfw.your_company.com:8443/openvsx/vscode/item under Settings → Antigravity IDE Settings → Editor. Not checked yet Block the code --install-extension CLI and VS Code Server from bypassing the firewall by applying a DNS override or by blocking marketplace.visualstudio.com, *.gallery.vsassets.io, *.gallerycdn.vsassets.io, and *.vscode-unpkg.net on editor machines or the HTTP proxy. Not checked yet Raise max_versions to allow installation of older VS Code extension versions that fall outside the newest max_versions plus two per release channel. Not checked yet
Route VS Code extension installs through the Socket Firewall by setting "extensions.gallery.serviceUrl" in settings.json to https://sfw.your_company.com:8443/vscode/vscode/gallery, or deploy the ExtensionGalleryServiceUrl policy via Group Policy, Intune, a macOS configuration profile, or /etc/vscode/policy.json on Linux for managed devices.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Route Cursor extension installs through the Socket Firewall using the openvsx route at https://sfw.your_company.com:8443/openvsx/vscode/gallery, configurable via Settings → VS Code Settings → marketplace service URL, or via Cursor's macOS profile or Windows Group Policy for managed fleets. Not checked yet Route Antigravity IDE extension installs through the Socket Firewall by setting the Gallery URL to https://sfw.your_company.com:8443/openvsx/vscode/gallery and the Item URL to https://sfw.your_company.com:8443/openvsx/vscode/item under Settings → Antigravity IDE Settings → Editor. Not checked yet Block the code --install-extension CLI and VS Code Server from bypassing the firewall by applying a DNS override or by blocking marketplace.visualstudio.com, *.gallery.vsassets.io, *.gallerycdn.vsassets.io, and *.vscode-unpkg.net on editor machines or the HTTP proxy. Not checked yet
1 more in Everything
Socket Firewall adds a vscode registry route for VS Code Marketplace and Open VSX Open VSX An open-source registry for VS Code extensions, maintained by the Eclipse Foundation, giving cyber tools a vendor-neutral alternative to the proprietary Microsoft Marketplace for distributing editor plugins. , with per-route verdicts, DNS-override support, and memory/concurrency tuning keys.
New supported platform Configure VS Code Marketplace proxying by adding a route with registry: vscode, upstream: https://marketplace.visualstudio.com, and an api_key (or PRIVATE_REGISTRY_KEY env var) to the firewall config. Not checked yet Set credentials for private registry auto-discovery via PATH_ROUTING_PRIVATE_REGISTRY_USERNAME and PATH_ROUTING_PRIVATE_REGISTRY_PASSWORD environment variables — the config file does not expand ${VAR} placeholders. Not checked yet Block unscanned extensions on the vscode route by setting ecosystem_params.vscode.allow_unknown: false — requires Socket to enable VS Code Marketplace scanning for the organization first (off by default). Not checked yet Tune VS Code Marketplace memory use and concurrency with ecosystem_params.vscode.max_all_versions_reads and ecosystem_params.vscode.history_cache_mb; set resources.limits.memory to at least 4Gi with the default 4 Helm workers. Not checked yet For DNS-override deployments, point marketplace.visualstudio.com at the firewall and block *.gallery.vsassets.io, *.gallerycdn.vsassets.io, *.vscode-unpkg.net for editor machines. Not checked yet
5 details in Everything
Socket Firewall adds vscode and openvsx registry routes for scanning code editor extensions, requiring Firewall 2.16.0+ and per-org opt-in.
New integration Scan VS Code Marketplace extensions by routing Microsoft VS Code through the vscode registry route (requires Socket Firewall 2.16.0 or later; must be enabled per organization — contact Socket). Not checked yet New integration Scan Open VSX Open VSX An open-source registry for VS Code extensions, maintained by the Eclipse Foundation, giving cyber tools a vendor-neutral alternative to the proprietary Microsoft Marketplace for distributing editor plugins. extensions by routing editors built on VS Code (Cursor, Antigravity, VSCodium) through the openvsx registry route, which gives each registry its own independent verdicts and per-platform-build checks. Not checked yet
2 details in Everything
Socket Fix adds --dynamic-sbom-inference to generate per-build-root SBOMs SBOMs A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. for Gradle, sbt, Maven, and .NET before computing fixes︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run Socket Fix with per-build-root SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation on a mixed JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. and .NET monorepo so each module's vulnerabilities are fixed independently.
copy
$ socket fix --dynamic-sbom-inference .
Limit dynamic SBOM generation to only Maven/Gradle/sbt builds, leaving .NET manifests untouched, to speed up fix runs in a JVM-only context.
copy
$ socket fix --dynamic-sbom-inference --dynamic-sbom-inference-ecosystems maven .
Limit dynamic SBOM generation to specific ecosystems with --dynamic-sbom-inference-ecosystems, accepting maven (Gradle, Maven, and sbt) or nuget (.NET) as comma-separated values or repeated flags; defaults to all supported ecosystems.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Socket: Generates a facts SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. per build root (Gradle, sbt, Maven, .NET) via --dynamic-sbom-inference, not one synthetic root; with --reach, reachability splits per︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Scan a monorepo with Gradle and Maven subprojects so each build root gets its own SBOM and reachability analysis instead of one merged result.
copy
$ socket scan --dynamic-sbom-inference --reach .
Restrict dynamic SBOM generation to .NET projects only, leaving npm, PyPI, Go, and other ecosystems scanned from their manifest files as usual.
copy
$ socket scan --dynamic-sbom-inference --dynamic-sbom-inference-ecosystems nuget .
Scan a Scala or Kotlin project that has no pre-existing manifest files by auto-generating them with the build tool before analysis.
copy
$ socket scan --auto-manifest .
Socket adds socket manifest dotnet to generate facts files for .NET projects and extends --dynamic-sbom-inference to auto-discover .NET, Gradle, Maven, and sbt builds.
New supported platform Generate Socket facts files for .NET solutions and projects with the new socket manifest dotnet subcommand, producing per-solution files such as App.sln.socket.facts.json plus individual project files for any project no solution builds. Not checked yet Updated supported platform Run socket scan create --dynamic-sbom-inference to recursively discover .NET, Gradle, Maven, and sbt build roots and generate a Socket facts SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. for each automatically, without a separate manifest step. Not checked yet
2 details in Everything
Socket adds per-project .NET reachability analysis and expands Python, Java, and Rust call-stack modeling︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Socket's reachability analysis now adds per-project reachability analysis for .NET projects scanned with dynamic SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. inference.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket's Python reachability analysis now models requests to handlers attached to standard library socketserver instances, improving soundness for applications that use Flask, werkzeug, or similar dependencies. Not checked yet Socket's Python reachability analysis now models Jinja2 template rendering and asyncio servers, improving soundness for applications that use these libraries. Not checked yet Socket's reachability analysis now reports workspace members as workspaces of their root project. Not checked yet Java and Rust reachability call stacks now name the JDK or Rust toolchain of standard-library frames. Not checked yet
+1 more
show less
Java and Rust reachability call stacks now give each file path relative to its module or crate. Not checked yet
Socket's reachability analysis now adds per-project reachability analysis for .NET projects scanned with dynamic SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. inference.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
5 more in Everything
Socket adds per-build SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation for Gradle, sbt, Maven, and .NET projects via --dynamic-sbom-inference-ecosystems︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Generate Socket facts only for .NET builds in a mixed-ecosystem repo, so reachability analysis uses precise build output rather than manifest files.
copy
$ socket scan --dynamic-sbom-inference-ecosystems nuget
Generate Socket facts for both JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. and .NET builds to get full reachability coverage across all supported build systems under the scan target.
copy
$ socket scan --dynamic-sbom-inference-ecosystems jvm,nuget
Filter which ecosystems get Socket facts files generated during a scan by passing --dynamic-sbom-inference-ecosystems with a comma-separated list of jvm and nuget values, leaving other ecosystems to scan from manifest files as before.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket now supports per-build SBOM generation for Gradle, sbt, Maven, and .NET projects, so reachability analysis runs from generated facts files rather than manifest files such as *.csproj and packages.lock.json. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
!
When the SBOM generation flag is used and no Gradle, sbt, Maven, or .NET build is found under the scan target, the scan now stops with an error instead of continuing silently.
Our best guess
New: Find PR Scans Faster with Search and Date Filters (2026-11-08)
Nov 8, 2026
·
issue 141
Socket adds repository, branch, PR number, title, and author search plus date-range filters to the PR Scans tab︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Find all PR scans by a specific author within a custom date range and share the resulting view with a teammate.
📍 In the Socket dashboard, go to Scans › PRs. Type the author name in the search box, then open Filter → Created and set a custom start and end date. Copy the URL from the browser address bar and share it.
Quickly audit which labels in your org have Security policy disabled so you can triage policy gaps.
📍 In the Socket dashboard, go to Repositories → Labels. Set the Security policy filter to Disabled to list all labels where the policy is off.
Search PR scan history by repository, branch, PR number, title, or author from the PRs tab on Scans — searches are case-insensitive and require at least two characters.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Filter PR scan history by creation or merge date using the new Filter → Created option, which replaces the old Last 90 days dropdown and supports both presets and specific date ranges; removing the filter shows all available PR scan history. Not checked yet Filter labels on the Repositories → Labels view by Security policy or License policy status (Enabled or Disabled). Not checked yet Search and filter state is now reflected in the page URL, making views bookmarkable and shareable. Not checked yet
Search PR scan history by repository, branch, PR number, title, or author from the PRs tab on Scans — searches are case-insensitive and require at least two characters.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Filter labels on the Repositories → Labels view by Security policy or License policy status (Enabled or Disabled). Not checked yet Search and filter state is now reflected in the page URL, making views bookmarkable and shareable. Not checked yet
1 more in Everything
New: Filter Alerts by Creation Date (2026-11-04)
Nov 4, 2026
·
issue 132
Socket adds a Created date filter to the Active Alerts page, with presets and custom ranges preserved in URLs and saved views.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Return to alerts created in the last 30 days by bookmarking the filtered URL — the Created date filter is preserved so the view reopens with the same range applied.
📍 In the Socket console, go to Active Alerts, open the Created date filter, select Last 30 days , then bookmark or save the resulting URL as a saved view.
Filter Active Alerts by creation date using preset ranges (Today, last 7, 14, 30, or 90 days) or a custom calendar range supporting between , since , and through modes, with filters preserved in URLs and saved views.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Full Scans date filter now supports the same presets (Today, last 7, 14, 30, or 90 days) and custom date range options. Not checked yet
Filter Active Alerts by creation date using preset ranges (Today, last 7, 14, 30, or 90 days) or a custom calendar range supporting between , since , and through modes, with filters preserved in URLs and saved views.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Organization alerts can now track multiple branches (2026-11-02)
Nov 2, 2026
·
issue 129
Socket now tracks multiple branches per repository for organization-wide alerts, supporting glob patterns and up to 5 branches per repo︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Track a canary or beta branch alongside main so production ring deployments all surface in org-wide alerts.
📍 Settings -> Scans -> Tracked Branches -> Add a branch name (e.g. canary ) or a glob expression (e.g. release/*) to begin receiving alerts, webhooks, and emails for that branch.
Register a full scan against a non-default branch via the API so it appears in organization alerts and triggers webhooks.
copy
$ curl -X POST https://socket.dev/api/full-scan \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/json' \
-d '{"branch": "canary", "set_as_pending_head": true}'
API users can now track non-default branches by setting the branch and set_as_pending_head fields when creating a full scan.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Organization-wide alerts now track multiple branches per repository (up to 5), with alerts broken down by label, repository, and branch in the dashboard. Not checked yet Add tracked branches using plain names or glob expressions via Settings -> Scans -> Tracked Branches to receive alerts, webhooks, and email notifications across branches such as beta, canary, or legacy. Not checked yet
API users can now track non-default branches by setting the branch and set_as_pending_head fields when creating a full scan.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
2 more in Everything
Socket schedules the removal of the GET /v0/report/view/{id} endpoint and changes Obfuscated code alert defaults on November 10︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Check the new full-scans endpoint to retrieve a scan report after the old view endpoint is retired.
copy
$ curl -s -H 'Authorization: Bearer <token>' 'https://api.socket.dev/v0/orgs/<org_slug>/full-scans/<full_scan_id>'
Verify the Sunset header on the deprecated endpoint before your migration deadline to confirm the retirement date.
copy
$ curl -sI -H 'Authorization: Bearer <token>' 'https://api.socket.dev/v0/report/view/<id>' | grep -i sunset
Migrate report view calls from the deprecated GET /v0/report/view/{id} endpoint to GET /v0/orgs/{org_slug}/full-scans/{full_scan_id} before November 20, 2026 — the old endpoint now advertises its retirement in a Sunset response header.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Keep Obfuscated code alerts after November 10 by opening Security Policy and setting Obfuscated code to Warn or Monitor instead of Inherit , or by adding a matching rule on the Policies page — the alert will be removed from the Balanced and Comprehensive preset defaults on that date. Not checked yet
Migrate report view calls from the deprecated GET /v0/report/view/{id} endpoint to GET /v0/orgs/{org_slug}/full-scans/{full_scan_id} before November 20, 2026 — the old endpoint now advertises its retirement in a Sunset response header.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
!
The `GET /v0/report/view/{id}` endpoint is retired on November 20, 2026; integrations using it must switch to `GET /v0/orgs/{org_slug}/full-scans/{full_scan_id}`.
Our best guess
!
The 'Obfuscated code' alert is removed from the 'Balanced' and 'Comprehensive' security policy presets on November 10, 2026; organizations relying on preset defaults will stop receiving this alert unless they explicitly set it to 'Warn' or 'Monitor'.
Our best guess
Obfuscated Code Alert Defaults Changing November 10 (2026-10-27)
Oct 27, 2026
·
issue 123
└──▷ BREAKING ON UPGRADE
!
The 'Obfuscated code' alert is removed from the 'Balanced' and 'Comprehensive' security policy presets on November 10, 2026; organizations relying on preset defaults will no longer receive these alerts unless they explicitly set 'Obfuscated code' to 'Warn' or 'Monitor' via Settings → Security Policy or the Policies page.
Our best guess
Socket Threat Intel Campaigns page now shows per-org blocked/detected status with drill-down to scans and Firewall events.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Determine whether a newly publicized malware campaign reached your org and whether Socket blocked or only detected it, then trace every affected repository and branch to the exact scan.
📍 In the Socket dashboard, go to Threat Intel → Campaigns. Locate the campaign in question and check the org-level status badge (Blocked by Socket, Detected in Firewall/SCA, or Not Detected). Click the campaign and open the Org Impact tab to see each affected package version, the repositories and branches that contained it, and first/last-seen dates. Click any date to open the corresponding scan report or Firewall event.
Adds per-organization campaign impact summaries — Blocked by Socket , Detected in Firewall/SCA, or Not Detected — to every malware campaign on the Threat Intel → Campaigns page, drawn from repository scans and Firewall event traffic.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet New Org Impact tab on each campaign shows each affected package and version separately, with the repositories, branches, and first/last-seen dates that link directly to the originating scan report or matching Socket Firewall events. Not checked yet Adds Blog and Affected Packages tabs to each campaign detail view, surfacing Socket write-ups and the complete list of affected packages alongside the impact data. Not checked yet
3 details in Everything
Socket: Adds token_prefix and token_last4 fields to token-list API responses, allowing key identification without parsing the masked display string.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Async endpoints for starting a fix computation and polling for results are now documented in the Fixes API, supporting supported parameters and result format to avoid timeouts on large projects or first runs. Not checked yet Adds repository access checks before computing or returning fixes for user OAuth sessions governed by repository or workspace policies, returning 403 for unfiltered repository endpoints. Not checked yet Adds current-role checks for OAuth requests so that role changes take effect on the next request, including for linked service-account requests. Not checked yet Organization settings are now accessible directly from the Settings link at the bottom of the dashboard sidebar. Not checked yet
Async endpoints for starting a fix computation and polling for results are now documented in the Fixes API, supporting supported parameters and result format to avoid timeouts on large projects or first runs. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
! API keys now use a new consistent masked format (e.g. sktsec_…Xy9Q); integrations that parse the previous masked format may need updating.
Faster bulk ticket creation for manifest alerts (2026-10-20)
Oct 20, 2026
·
issue 114
Socket adds bulk ticket creation for manifest alerts across Jira, Linear, Asana, and ClickUp, with shift-click range selection.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Select multiple manifest alerts across repositories and create one Jira ticket per repo/manifest in a single action.
📍 In the Socket dashboard, navigate to your manifest alerts list. Shift-click to select the desired range of alerts, then choose Create tickets and select Jira (or Linear, Asana, or ClickUp) to generate one ticket per repository and manifest file.
Bulk-create Jira, Linear, Asana, and ClickUp tickets for manifest alerts (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Missing lockfile ), one ticket per repository and manifest file, scoped to the selected repository and branch. Not checked yet Shift-click to select a range of alerts for bulk actions. Not checked yet
2 details in Everything
OAuth access stays in sync with role changes (2026-10-15)
Oct 15, 2026
·
issue 114
Socket OAuth access now enforces current role permissions on every request, so role changes take effect immediately.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
For organizations with current-role checks enabled, OAuth token requests now validate both the token's granted scopes and the user's current role permissions, with role changes taking effect on the next request.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Linked service-account OAuth requests now check current service-account permissions alongside granted token scopes. Not checked yet
For organizations with current-role checks enabled, OAuth token requests now validate both the token's granted scopes and the user's current role permissions, with role changes taking effect on the next request.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Socket for Origin brings automatic dependency scanning and security findings to Origin (Cursor) pull requests via the Origin App Marketplace.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Connect Socket to Origin so every pull request automatically gets dependency security checks without leaving your Origin workflow.
📍 In the Origin App Marketplace, find Socket, click Install, authorize your Socket organization, and confirm the connection. From that point, Socket runs a Socket Security / Dependency scan check automatically on every PR open and commit push.
Adds Socket for Origin integration in the Origin App Marketplace, enabling automatic dependency scans on Origin pull requests when opened or new commits are pushed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Posts a Socket Security / Dependency scan check on Origin pull requests, showing scan progress, a policy-based verdict, and a link to the full report — with a rerun button directly in Origin. Not checked yet Posts PR comments with dependency overviews, scores, severity labels, and report links, updating automatically as the PR changes. Not checked yet Scans supported manifests and lockfiles — including dependency changes in monorepo workspaces — by comparing the target branch with Origin's proposed merge result. Not checked yet
4 details in Everything
Socket reachability analysis gains broader facts-file support, Python/PyTorch precision improvements, and overhauled fix engines for Maven, Gradle, sbt, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Cargo, RubyGem︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Recognises Socket facts files matching any *.socket.facts.json naming pattern (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ pom.xml.socket.facts.json). Not checked yet JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. reachability analysis now uses the per-subproject classpath from the Socket CLI's compute-artifacts sidecar when one is provided. Not checked yet Socket Fix refuses a pnpm upgrade that needs a new version of a private package, and instructs the user to run it where the registry is reachable. Not checked yet Performance, recall, and out-of-memory out-of-memory An out-of-memory condition: a program requests more memory than the system or device can provide. The allocation fails or the operating system may stop the process. handling improvements for the JavaScript/TypeScript, PHP, and JVM reachability analyses. Not checked yet Soundness and memory usage improvements for the Python reachability analysis. Not checked yet
Recognises Socket facts files matching any *.socket.facts.json naming pattern (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ pom.xml.socket.facts.json). Not checked yet Socket Fix refuses a pnpm upgrade that needs a new version of a private package, and instructs the user to run it where the registry is reachable. Not checked yet
3 more in Everything
Socket Fix gains scoped override/resolution writing when a parent version range blocks a fix, and now lists fixes it could not apply with a non-zero exit code.
Updated supported platform Socket Fix can now write a scoped override or resolution when a parent's version range is the only thing blocking a fix. Not checked yet Socket Fix now lists the fixes it could not apply and exits with a non-zero code instead of reporting them as applied. Not checked yet
2 details in Everything
Socket Fix gains scoped-override writing, non-zero exit on failed fixes, PyTorch-aware Python analysis, and broader *.socket.facts.json file recognition.
Recognises Socket facts files matching any *.socket.facts.json pattern (e.g. pom.xml.socket.facts.json) for broader project discovery. Not checked yet Socket Fix can now write a scoped override or resolution when a parent version range is the only thing blocking a fix. Not checked yet Socket Fix now lists fixes it could not apply and exits with a non-zero code instead of silently reporting them as applied. Not checked yet Updated supported platform More precise modeling of PyTorch in the Python reachability analysis prevents analysis blow-ups in projects that use it. Not checked yet
4 details in Everything
Socket Fix overhauls dependency upgrades for Maven, Gradle, sbt, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Cargo, RubyGems, and pnpm with tool-native resolution semantics︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. reachability analysis uses the per-subproject classpath from the Socket CLI's compute-artifacts sidecar when one is provided.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Socket Fix for pnpm now refuses an upgrade that needs a new version of a private package, and instructs running it where the registry is reachable. Not checked yet
2 details in Everything
└──▷ TRY IT
Poll migration status in CI to gate whether to send policy/rule writes with or without dry_run — only switching live when state is accepted or auto_finalized.
copy
$ curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/status
New GET /v0/orgs/{org_slug}/alert-policies/migration/status endpoint reveals your org's policy migration state and which config decides alerts now.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Poll your org's migration status in CI to gate whether to send policy/rule writes with or without dry_run, based on the current state field.
copy
$ curl -u "$SOCKET_API_TOKEN:" \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/status
Adds GET /v0/orgs/{org_slug}/alert-policies/migration/status to return migration state (null, pending, previewing, accepted, or auto_finalized), finalization timestamps (finalized_at, deadline_at, window_end_at, deadline_admin_paused_at), and two booleans (alert_policies_enabled, legacy_evaluation_enabled) showing which configuration currently drives alert actions — requires the alert-policy:list scope and org-wide repository access, costs 1 quota unit per call.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Socket reachability analysis gains Go 1.27 support, pnpm catalog resolution, and per-pattern broken vulnerability reporting︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin all pnpm catalog dependencies to exact versions during a fix run, so catalog entries are written as bare versions rather than range expressions.
copy
$ socket fix --range-style pin
Supports dependencies declared through a pnpm catalog — entries like 'tap': 'catalog:' or 'tap': 'catalog:tools' now resolve correctly, preserving range operators (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ =19.2.5 upgraded to =21.8.0), with --range-style pin writing the bare version. Not checked yet Reports broken vulnerability patterns per pattern, with the affected package version, for the JavaScript, Go, and Python reachability analyses. Not checked yet
Supports dependencies declared through a pnpm catalog — entries like 'tap': 'catalog:' or 'tap': 'catalog:tools' now resolve correctly, preserving range operators (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ =19.2.5 upgraded to =21.8.0), with --range-style pin writing the bare version. Not checked yet
1 more in Everything
Socket reachability analysis adds Go 1.27 support, Python pickle hook modeling, and lower peak memory for large repos.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports Go 1.27 projects in the Go reachability analysis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Models calls to pickle.{Pickler,Unpickler} hooks through load and dump in the Python reachability analysis. Not checked yet Lowers peak memory use when scanning large repositories. Not checked yet
Supports Go 1.27 projects in the Go reachability analysis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
2 more in Everything
└──▷ TRY IT
Poll migration status in CI to gate whether to send live policy writes or fall back to dry_run — avoid sending writes that return errors during the pending or previewing states.
copy
$ curl -u "$SOCKET_API_TOKEN:" \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/status
Socket reachability engine adds PHP support, --reach-version override, dynamic JS dispatch, Go/Rust analysis improvements, and smarter socket fix for Go modules︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan without waiting for a Socket CLI release — useful when a newer engine fixes a false-positive for your stack.
copy
$ socket scan reach --reach-version 15.10.38 .
The --entry-points flag now applies only to the scanned project's own root instead of leaking into every discovered subproject. Not checked yet Performance improvements for Python reachability analysis on projects using 3rd-party serializers like Pydantic. Not checked yet
2 more in Everything
New GET /v0/orgs/{org_slug}/alert-policies/migration/status endpoint reveals your org's Policies migration state in real time.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Check whether your org has crossed into accepted or auto_finalized before deciding whether to send policy/rule writes with or without dry_run.
copy
$ curl -u "$SOCKET_API_TOKEN:" \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/status
Adds GET /v0/orgs/{org_slug}/alert-policies/migration/status to report where an organization stands in the alert-policy migration, returning state (null, pending, previewing, accepted, or auto_finalized), the booleans alert_policies_enabled and legacy_evaluation_enabled, and timestamps (finalized_at, deadline_at, window_end_at, deadline_admin_paused_at) — all as ISO ISO A widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability. -8601 strings or null.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Requires the alert-policy:list scope and organization-wide repository access on the API token; a repository-restricted token returns an error, and each call consumes 1 unit of quota. Not checked yet
2 details in Everything
Socket's Coana reachability engine gains PHP support, workspace grouping, dynamic JS dispatch, and smarter fix attribution via --dry-run --output-file︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan — useful when you need to reproduce results from an earlier engine or test a newer one before it ships in the CLI bundle.
copy
$ socket scan reach --reach-version 15.10.38 .
Adds --reach-version flag to socket scan reach to run a specific Coana engine version instead of the bundled pinned one.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds withheldFixes field to the --dry-run --output-file JSON output, naming versions and flags that blocked an automatic fix. Not checked yet Enables reachability analysis for PHP/Composer projects when running via the Socket CLI, with subdirectory Composer projects analyzed in their own directory. Not checked yet Supports vulnerability patterns that identify vulnerable Rust/Cargo code by source location, with semver range scoping so a pattern only applies to crate versions within its range. Not checked yet JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. /Java scans now support multiple independent Maven/Gradle/SBT SBT A build tool for Scala and Java projects, maintained by the open-source community, that handles compilation, dependency resolution, and packaging using an incremental build model to speed up iterative development. build roots in a single repository. Not checked yet
+5 more
show less
JavaScript/TypeScript reachability analysis now approximates unresolved dynamic property reads and calls (e.g. obj[key]()) instead of dropping them, catching reachable code behind dynamic dispatch. Not checked yet Reachability reports are now streamed to disk rather than serialized as a single string, removing the ~512 MiB RangeError: Invalid string length limit on large repositories. Not checked yet Maven artifact resolution now tries remaining public repositories after a failed download instead of stopping at the first failure. Not checked yet Package downloads are now retried on transient network failures, with distinct fast-fail behaviour for missing packages, rejected certificates, and unresolvable hosts. Not checked yet Prefers uv over pyenv when a specific Python interpreter is required for reachability analysis. Not checked yet
Adds --reach-version flag to socket scan reach to run a specific Coana engine version instead of the bundled pinned one.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds withheldFixes field to the --dry-run --output-file JSON output, naming versions and flags that blocked an automatic fix. Not checked yet Enables reachability analysis for PHP/Composer projects when running via the Socket CLI, with subdirectory Composer projects analyzed in their own directory. Not checked yet Supports vulnerability patterns that identify vulnerable Rust/Cargo code by source location, with semver range scoping so a pattern only applies to crate versions within its range. Not checked yet
6 more in Everything
Socket: Adds --reach-version flag to socket scan reach to run a different pinned Coana engine version than the one bundled with the Socket CLI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan to test a newer engine without upgrading the CLI.
copy
$ socket scan reach --reach-version 15.10.38 .
Inspect which fixes were withheld by a policy flag (e.g. --disable-major-updates) without making any changes.
copy
$ socket scan reach --dry-run --output-file results.json . && jq '.withheldFixes' results.json
Enables reachability analysis for PHP/Composer projects when running through the Socket CLI; a Composer project in a subdirectory is now analyzed in its own directory rather than at the repository root. Not checked yet Adds withheldFixes field to --dry-run --output-file JSON output, naming the version and responsible flag when compute-fixes-and-upgrade-purls cannot apply a fix due to a policy constraint such as --disable-major-updates. Not checked yet npm, pnpm, and yarn workspace packages are now grouped and analyzed together under their workspace root when running reachability analysis via the Socket CLI. Not checked yet Reachability scans now survive transient Socket backend failures by retrying with exponential backoff, exiting with a dedicated exit code for Socket-side outages instead of crashing. Not checked yet Improved JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. /Java reachability analysis with better parity between source-based and bytecode-based analyses and improved support for Kotlin and Scala constructs such as delegated properties and object declarations. Not checked yet
+1 more
show less
Go reachability analysis gains better handling of timeouts and improved support for push-style //go:linkname directives. Not checked yet
Enables reachability analysis for PHP/Composer projects when running through the Socket CLI; a Composer project in a subdirectory is now analyzed in its own directory rather than at the repository root. Not checked yet Adds withheldFixes field to --dry-run --output-file JSON output, naming the version and responsible flag when compute-fixes-and-upgrade-purls cannot apply a fix due to a policy constraint such as --disable-major-updates. Not checked yet
4 more in Everything
Socket's Coana reachability engine gains PHP support, smarter Go/Rust/JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. analysis, and a new --reach-version override flag.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin a specific Coana engine version for a scan without waiting for a Socket CLI release — useful when a newer engine fixes a false-positive or adds coverage you need today.
copy
$ socket scan reach --reach-version 15.10.38 .
Adds withheldFixes field to --dry-run --output-file JSON output, attributing which flag (e.g. --disable-major-updates) blocked a fix and naming the withheld version. Not checked yet JVM/Java reachability analysis now supports scans containing multiple independent Maven/Gradle/SBT SBT A build tool for Scala and Java projects, maintained by the open-source community, that handles compilation, dependency resolution, and packaging using an incremental build model to speed up iterative development. build roots. Not checked yet Performance improvements for the Python reachability analysis on projects that use third-party serializers like Pydantic. Not checked yet
Adds withheldFixes field to --dry-run --output-file JSON output, attributing which flag (e.g. --disable-major-updates) blocked a fix and naming the withheld version. Not checked yet
2 more in Everything
New GET /v0/orgs/{org_slug}/alert-policies/migration/status endpoint reveals where your org stands in Socket's Policies migration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Check whether your org has completed the migration before deciding whether to send policy writes with or without dry_run in a CI script.
copy
$ curl -u "$SOCKET_API_TOKEN:" \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/status
Adds GET /v0/orgs/{org_slug}/alert-policies/migration/status to query your organization's current position in the alert-policy migration, returning state, alert_policies_enabled, legacy_evaluation_enabled, finalized_at, deadline_at, window_end_at, and deadline_admin_paused_at fields.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Socket: Adds withheldFixes field to --dry-run --output-file JSON output, naming versions and flags that blocked a fix (e.g. --disable-major-updates).
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan without waiting for a Socket CLI update — useful to test a newer engine or lock a known-good one in CI.
copy
$ socket scan reach --reach-version 15.10.38 .
Adds grouping of npm, pnpm, and yarn workspace packages so they are analyzed together under their workspace root during reachability scans. Not checked yet Adds approximation of unresolved dynamic property reads and calls (e.g. obj[key]()) in JavaScript/TypeScript reachability analysis so reachable code behind dynamic dispatch is no longer missed. Not checked yet Streams large reachability reports to disk instead of serializing them as a single JavaScript string, removing the ~512 MiB RangeError: Invalid string length limit. Not checked yet --entry-points now applies only to the scanned project's own root instead of leaking into every discovered subproject. Not checked yet Maven artifact resolution now tries remaining public repositories after a failed download instead of giving up after the first failure. Not checked yet
+1 more
show less
Package downloads in reachability analysis are now retried on transient network failures, with immediate failure on a missing package, rejected certificate, or unresolvable host, and the failure reason is named. Not checked yet
Adds grouping of npm, pnpm, and yarn workspace packages so they are analyzed together under their workspace root during reachability scans. Not checked yet
5 more in Everything
Socket's Coana reachability engine gains PHP support, smarter fix attribution, Go/Rust/JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. analysis improvements, and JS dynamic dispatch coverage︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan without waiting for a Socket CLI update — useful when a newer engine version fixes a language-specific analysis issue.
copy
$ socket scan reach --reach-version 15.10.38 .
Adds --reach-version flag to socket scan reach to override the bundled Coana engine version and run a specific one instead.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Reachability scans now survive transient Socket backend failures with exponential-backoff retries, a human-readable outage explanation, and a dedicated exit code instead of a stack trace. Not checked yet Supports vulnerability patterns that identify vulnerable Rust/Cargo code by source location, including semver range scoping so a pattern only applies to crate versions within its range. Not checked yet Unresolved dynamic property reads and calls (e.g. obj[key]() where key is not a constant) in JavaScript/TypeScript are now approximated rather than dropped, so reachable code behind dynamic dispatch is no longer missed. Not checked yet Adds support for multiple independent Maven/Gradle/SBT SBT A build tool for Scala and Java projects, maintained by the open-source community, that handles compilation, dependency resolution, and packaging using an incremental build model to speed up iterative development. build roots within a single JVM/Java reachability scan. Not checked yet
+2 more
show less
Maven artifact resolution now tries remaining public repositories after a failed download instead of halting on the first failure; package downloads are retried on transient network failures with immediate failure on missing packages, rejected certificates, or unresolvable hosts. Not checked yet Prefers uv over pyenv when a specific Python interpreter is required for reachability analysis. Not checked yet
Adds --reach-version flag to socket scan reach to override the bundled Coana engine version and run a specific one instead.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Supports vulnerability patterns that identify vulnerable Rust/Cargo code by source location, including semver range scoping so a pattern only applies to crate versions within its range. Not checked yet
5 more in Everything
Socket reachability engine adds PHP support, JS dynamic dispatch approximation, --reach-version override, and smarter socket fix for Go and Cargo.
└──▷ TRY IT
Pin a specific Coana engine version for a reachability scan, e.g. to test a newer engine before it ships in the CLI bundle.
copy
$ socket scan reach --reach-version 15.10.38 .
Inspect which fix versions were withheld by policy flags during a dry-run, using the structured JSON output.
copy
$ socket scan reach --dry-run --output-file results.json . && jq '.withheldFixes' results.json
Adds --reach-version flag to socket scan reach to run a different Coana engine version than the one bundled with the Socket CLI. Not checked yet Adds withheldFixes field in --dry-run --output-file JSON output when compute-fixes-and-upgrade-purls cannot apply a fix because a flag such as --disable-major-updates withheld the only patched version. Not checked yet Enables reachability analysis for PHP/Composer projects when running via the Socket CLI; a Composer project in a subdirectory is now analyzed in its own directory rather than at the repository root. Not checked yet npm, pnpm, and yarn workspace packages are now grouped and analyzed together under their workspace root when running reachability analysis via the Socket CLI. Not checked yet JavaScript/TypeScript reachability analysis now approximates unresolved dynamic property reads and calls (e.g. obj[key]() where key is not a constant) instead of dropping them, so reachable code behind dynamic dispatch is no longer missed. Not checked yet
+6 more
show less
Rust reachability analysis adds support for vulnerability patterns that identify vulnerable code by source location, with semver range scoping so a pattern only applies to crate versions within its range. Not checked yet JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. /Java reachability analysis adds improved support for Kotlin and Scala constructs such as delegated properties and object declarations. Not checked yet Reachability scans now retry with exponential backoff on transient Socket backend failures and exit with a dedicated exit code for Socket-side outages instead of crashing. Not checked yet Reachability reports are now streamed to disk (no longer limited by the ~512 MiB JavaScript string ceiling), and evidence stacks are capped at 3 per alert (down from 10), keeping the shortest stacks. Not checked yet Python reachability analysis now prefers uv over pyenv when a specific Python interpreter is required. Not checked yet Go reachability analysis adds better handling of timeouts and improved support for push-style //go:linkname directives. Not checked yet
Adds --reach-version flag to socket scan reach to run a different Coana engine version than the one bundled with the Socket CLI. Not checked yet Adds withheldFixes field in --dry-run --output-file JSON output when compute-fixes-and-upgrade-purls cannot apply a fix because a flag such as --disable-major-updates withheld the only patched version. Not checked yet Enables reachability analysis for PHP/Composer projects when running via the Socket CLI; a Composer project in a subdirectory is now analyzed in its own directory rather than at the repository root. Not checked yet
8 more in Everything
Socket API write endpoints now accept ?dry_run=true to validate policy, rule, and resolution requests without saving anything.
└──▷ TRY IT
Validate a new alert policy before migration cutover — confirms the payload is accepted and previews the assigned id without actually creating the policy.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{"name": "Production", "description": "Stricter handling for production services", "baseline": "balanced"}' \
"https://api.socket.dev/v0/orgs/$ORG/alert-policies?dry_run=true"
Test a resolution payload against a specific alert selector to confirm scope and auth before committing — useful when you want to avoid accidentally suppressing alerts org-wide.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{"reason": "other", "comment": "accepted risk", "vigil_selector": {"finding.alertType": "criticalCVE", "artifact.type": "npm", "artifact.name": "lodash"}}' \
"https://api.socket.dev/v0/orgs/$ORG/alerts/resolutions?dry_run=true"
Confirm a policy delete is targeting the right policy before running the destructive call in a migration script.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X DELETE \
"https://api.socket.dev/v0/orgs/$ORG/alert-policies/$POLICY_ID?dry_run=true"
Adds ?dry_run=true query parameter to policy, rule, and resolution write endpoints — returns the same response body a real write would, including the id/uuid, but creates, updates, or deletes nothing. Not checked yet Supports dry_run on POST /orgs/{org_slug}/alert-policies, PUT /orgs/{org_slug}/alert-policies/{policy_id}, DELETE /orgs/{org_slug}/alert-policies/{policy_id}, POST /orgs/{org_slug}/alert-policies/{policy_id}/rules, PUT /orgs/{org_slug}/alert-policies/{policy_id}/rules/{rule_id}, DELETE /orgs/{org_slug}/alert-policies/{policy_id}/rules/{rule_id}, and POST /orgs/{org_slug}/alerts/resolutions. Not checked yet Dry-run creates return HTTP 200 with dry_run: true in the body (not 201); dry-run deletes return { "dry_run": true } instead of { "result": "success" }; dry-run updates return 200 with the updated body plus dry_run: true. Not checked yet Accepts true, 1, or yes (case-insensitive, surrounding space ignored) to enable dry-run; false, 0, no, or omitted for a real write; any other value (e.g. ture, on) returns 400: dry_run must be true, 1, yes, false, 0, or no; conflicting repeated values return 400: dry_run has conflicting values. Not checked yet Auth and quota rules match real writes: alert-policy:create/:update/:delete for policy and rule endpoints, alert-resolution:create for resolutions; repository-restricted tokens still receive 403 on policy writes; each dry-run call consumes 1 unit of quota. Not checked yet
5 details in Everything
Socket adds POST /orgs/{org_slug}/alert-policies/migration/translate to convert legacy alert triage payloads into new resolution or policy-rule requests.
└──▷ TRY IT
Translate a batch of legacy triage rules to preview what alert resolutions and policy rules they become before committing to migration.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{
"alertTriage": [
{
"packageType": "npm",
"packageName": "lodash",
"alertType": "criticalCVE",
"note": "accepted risk",
"state": "ignore"
}
]
}' \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/migration/translate
Dry-run a translated policy-rule body to validate it against the Default policy without writing it — safe to run before confirming migration.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{
"name": "in [email protected]",
"action": "monitor",
"note": null,
"vigil_selector": {
"artifact.type": "npm",
"artifact.name": "react",
"artifact.version": "19.2.8"
}
}' \
'https://api.socket.dev/v0/orgs/$ORG/alert-policies/default/rules?dry_run=true'
New POST /orgs/{org_slug}/alert-policies/migration/translate endpoint accepts the same alertTriage array (1–100 entries) used by POST /orgs/{org_slug}/triage/alerts and returns translated alert_resolution or alert_policy_rule request bodies without writing anything. Not checked yet Supports ?dry_run=true on rule-body POSTs so practitioners can validate translated policy-rule payloads before confirming migration. Not checked yet Response always returns two arrays — translations (with index, target, method, path, and body) and untranslatable (with index, code, and reason) — so partial batches surface per-entry failures without dropping the rest. Not checked yet Defines structured untranslatable error codes: inherit_not_translatable, alert_key_not_translatable, matches_all_alerts, filter_not_translatable, and note_too_long, each with actionable remediation guidance. Not checked yet Accepts any one of triage:alerts-update, alert-policy:read, or alert-resolution:create token scopes; consuming 1 unit of quota per call. Not checked yet
+4 more
show less
Legacy ignore entries that can be expressed as alert-type/package filters translate to alert_resolution targets (reason always other); those with fixAvailable, cvssScoreCmp, reachability, or kevs filters translate to alert_policy_rule targets instead. Not checked yet Legacy block entries translate to alert_policy_rule with error action; warn and monitor entries become policy rules with their respective actions. Not checked yet Policy-rule translations always target the Default policy at /alert-policies/default/rules; sending the same body to /alert-policies/{policy_id}/rules applies it to a labeled policy. Not checked yet Scoped npm package names (e.g. @scope/pkg) stored whole in packageName are automatically split into artifact.namespace and artifact.name in the returned selector. Not checked yet
9 details in Everything
Socket adds dry-run support to POST /alerts/resolutions and a triage-payload translation utility.
└──▷ TRY IT
Validate a resolution payload against the API before committing it — useful for testing migrated triage rules without side effects.
copy
$ POST /alerts/resolutions?dry_run=true
Adds ?dry_run=true query parameter to POST /alerts/resolutions to validate a resolution payload without saving it. Not checked yet Adds a Translating Alert Triage Payloads utility to convert existing Alert Triage ignore-rule request bodies into the resolutions format. Not checked yet
2 details in Everything
Socket adds ?dry_run=true to policy/rule write endpoints so you can test API changes before confirming a migration.
Adds ?dry_run=true query parameter to policy and rule write endpoints: returns 200 and validates the write without saving anything, letting you test API integrations before confirming the Policies migration. Not checked yet During the Policies migration preview, real policy and rule writes return 409 until the migration is confirmed — use ?dry_run=true to safely test writes in the interim. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! While your organization is previewing the migration to Policies, real policy and rule write API calls return 409 until the migration is confirmed.
Socket adds Microsoft Teams as a notification channel with per-channel subscriptions, severity filters, and Adaptive Card Adaptive Card A JSON-defined UI snippet, maintained by Microsoft, that renders natively in host apps like Teams or Outlook, letting tools surface structured data without building platform-specific UI code. digests.
└──▷ HOW TO FIND IT
Connect a Teams channel to Socket so critical supply chain alerts land in your security team's channel automatically.
📍 In Socket, go to Settings → Integrations → Notifications → Create Channel, select Microsoft Teams , enter a channel name, and paste the HTTP POST URL copied from your Microsoft Workflows 'Post to a channel when a webhook request is received' flow. Socket will send a test Adaptive Card; a successful test marks the channel as Active.
Route only critical supply chain risk alerts for a specific repository to a dedicated engineering Teams channel, keeping noise out of the general security channel.
📍 In Socket, go to Settings → Integrations → Notifications → Create Subscription, choose the alert created event, set filters to category: supply chain risk , severity: critical, and the target repository, then select your Microsoft Teams channel as the destination.
Adds Microsoft Teams as a notification destination in Settings → Integrations → Notifications , configured via a Microsoft Workflows incoming webhook (HTTP POST URL) alongside the existing email channel. Not checked yet New subscription model lets owners and admins route organization alerts and supply chain attack campaign notifications to specific Teams channels, filtered by alert category (supply chain risk, vulnerability, quality, maintenance, license), severity, Socket priority, repository, or package ecosystem. Not checked yet Delivers notifications as structured Adaptive Cards Adaptive Cards An open-source card schema from Microsoft that lets apps render structured UI snippets — buttons, text, images — natively inside any host surface, so a tool can push rich, interactive notifications without owning the renderer. summarizing alert totals by severity, affected repository count, individual finding previews, and a direct link to the Socket dashboard. Not checked yet Groups related alert activity into digests before posting to Teams, preventing channel flooding when a scan surfaces many alerts at once. Not checked yet Attack campaign notifications indicate whether affected packages are present in the organization — showing impacted repositories or confirming no monitored repositories are affected — without requiring manual per-repository checks. Not checked yet
5 details in Everything
Socket adds Asana alert ticketing, PHP/Composer beta support, and Firefox extension scanning
New Asana integration lets teams create and manage Asana tasks from Socket alerts, either manually or via ticketing rules that filter by event, type, priority, and repository — with configurable sync between task and alert status; available in beta on Business and Enterprise plans. Not checked yet PHP and Composer support promoted from Experimental to Beta and now available to all Socket users; PHP reachability analysis is generally available for Team plan customers and above without requiring Experimental access. Not checked yet New Firefox extension scanning covers every extension in Mozilla's official add-ons directory, monitoring for permission changes, network activity, malware, credential and clipboard theft, data exfiltration data exfiltration Moving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels. , remote loading, obfuscation, and impersonation; available in Experimental for Enterprise customers. Not checked yet
3 details in Everything
Socket adds Microsoft Edge Add-ons extension monitoring, bringing malware, credential-theft, and version-change detection to Edge.
└──▷ HOW TO FIND IT
Enable Edge extension coverage for your enterprise org — reach out to your Socket account team or contact Socket to get started with the Experimental rollout.
📍 In the Socket dashboard, contact your Socket account team to enable Edge coverage under the Experimental tier for your enterprise organization.
Adds continuous analysis of extensions published through Microsoft Edge Add-ons, covering malware, credential and clipboard theft, data exfiltration data exfiltration Moving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels. , remote code loading, obfuscation, and impersonation — the same detections previously available for Chrome and Firefox. Not checked yet Enables version-change comparison for Edge extensions, surfacing meaningful differences in code, permissions, network activity, and behavior between releases under the same extension identity. Not checked yet Identifies command-and-control infrastructure, suspicious endpoints, remote payload sources, and changes in domains contacted by Edge extensions. Not checked yet Connects related extensions across stores through reused code, shared infrastructure, publisher patterns, and coordinated campaigns. Not checked yet Closes cross-store coverage gap by pairing Chrome Web Store analysis (including Chrome extensions Edge users can install) with new Microsoft Edge Add-ons analysis. Not checked yet
5 details in Everything
Socket for ClickUp integration launches in beta, enabling bi-directional alert-to-task sync with automated ticketing rules.
└──▷ HOW TO FIND IT
Set up the ClickUp integration in Socket to start routing alerts as tasks into your team's existing ClickUp workflows.
📍 In the Socket dashboard, go to Settings → Integrations → ClickUp and click Connect.
New ClickUp integration Beta lets teams create ClickUp tasks from Socket alerts via Settings → Integrations → ClickUp in the Socket dashboard. Not checked yet Automated ticketing rules route matching Socket findings into a chosen ClickUp Workspace and List, with configurable priority (Urgent , High , Normal , Low , or Auto to map Socket priority automatically), tags, and assignee. Not checked yet Bi-directional status sync keeps Socket alerts and ClickUp tasks updated: clearing an alert can move the linked task to completed, and closing or completing a task in ClickUp can triage-ignore the corresponding Socket alert. Not checked yet ClickUp task updates, status changes, and deletions are delivered to Socket via Workspace webhooks, giving security monitors and engineers a shared view of issue status. Not checked yet Manual task creation available for individual alerts via the Create Ticket button in the Socket alert view, with selection of target ClickUp Workspace and List (displayed with full Space / List or Space / Folder / List path). Not checked yet
5 details in Everything
New: Asana integration for alert ticketing (2026-08-25)
Aug 25, 2026
·
issue 057
Socket adds Asana integration Beta for creating and managing tasks from alerts via manual action or ticketing rules.
Adds Asana integration (beta, Business and Enterprise plans) to create and manage Asana tasks directly from Socket alerts. Not checked yet Supports ticketing rules that filter alerts by event, type, priority, repository, and other attributes to automate Asana task creation. Not checked yet Allows configuring Asana workspace, project, tags, and assignee per ticketing rule, with bi-directional status sync between linked tasks and alerts. Not checked yet
3 details in Everything
New: Asana integration for alert ticketing
Aug 25, 2026
· release notes
Socket enables Asana task management from alerts via UI configuration.
New integration with Asana for alert ticketing. Not checked yet
1 detail in Everything
Socket launches native Asana integration with manual ticket creation, automated ticketing rules, and two-way sync.
└──▷ HOW TO FIND IT
Connect an Asana workspace to your Socket organization so alerts can be routed as trackable tasks.
📍 In the Socket dashboard, go to Settings → Integrations → Asana and click Connect. Authorize via OAuth — no third-party admin console required. The connected workspace name, connecting user, and status will appear in the Socket dashboard.
Set up an automated ticketing rule to route high-priority supply chain alerts directly to the right Asana project without manual triage.
📍 In the Socket dashboard, go to Settings → Integrations → Asana → ticketing rules. Step 1: select the alert events that trigger the rule. Step 2: add conditions (e.g., type = supply chain, priority = high). Step 3: select the connected Asana workspace and target project. Step 4: add tags and assign to an Asana user. Step 5: configure two-way sync behavior — e.g., mark Asana task complete when alert clears, and triage-ignore the Socket alert when the Asana task is completed.
New Settings → Integrations → Asana UI in the Socket dashboard lets an Owner or Admin connect one or more Asana workspaces via OAuth, with no separate app to install. Not checked yet Adds a Create Ticket button on any Socket alert to manually create a linked Asana task — selecting workspace, project, tags, and assignee — with a bidirectional link between the alert and the task. Not checked yet Two-way sync keeps Asana tasks and Socket alerts current: Socket can mark an Asana task complete when an alert clears, and completing the Asana task can triage-ignore the linked Socket alert. Not checked yet
3 details in Everything
Socket adds --dynamic-sbom-inference flag to Node CLI for per-subproject JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. reachability analysis across Gradle, sbt, and Maven builds.
└──▷ TRY IT
Run a reachability scan on a multi-module Gradle, sbt, or Maven repo so each subproject is analyzed independently with an accurate dependency graph from the build tool.
copy
$ socket scan create --reach --dynamic-sbom-inference
Pre-generate Socket facts files for a JVM build before running a Python CLI reachability scan (or when the build tool must be invoked separately).
copy
$ socket manifest dynamic-sbom-inference
Adds --dynamic-sbom-inference flag to socket scan create --reach in the Node CLI, triggering the build tool to generate a Socket facts file so every Gradle, sbt, and Maven build under the scan target is analyzed per-subproject rather than as a single unit — yielding faster scans on large repos and more accurate dependency graphs. Not checked yet Adds socket manifest setup --dynamic-sbom-inference to configure per-project defaults one build at a time for repositories containing several JVM builds. Not checked yet Adds socket manifest dynamic-sbom-inference as a standalone pre-generation step, enabling Python CLI users (and sbt/Gradle-without-lockfile users) to produce the required facts files before running a scan. Not checked yet
3 details in Everything
Socket Kotlin scans now support full reachability analysis with dynamic SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. inference per Gradle subproject.
└──▷ TRY IT
Run a full reachability scan across all Gradle subprojects in a Kotlin repo, generating manifests automatically without a pre-existing SBOM.
copy
$ socket scan create --reach --dynamic-sbom-inference
Adds --reach --dynamic-sbom-inference flags to socket scan create for full application reachability scans on Kotlin projects, analyzing and reporting reachability per Gradle subproject using the dependency graph Gradle itself resolves. Not checked yet
1 detail in Everything
PHP and Composer support is now in beta (2026-08-21)
Aug 21, 2026
·
issue 057
Socket PHP and Composer support graduates to Beta with reachability analysis now GA for Team plans
PHP and Composer support is now in Beta and available to all Socket users (previously Experimental). Not checked yet PHP reachability analysis is now generally available for Team plan customers and above, with no Experimental access required — includes precomputed reachability and full application reachability. Not checked yet
2 details in Everything
New: Firefox extension protection (2026-08-20)
Aug 20, 2026
·
issue 057
Socket adds Firefox extension scanning, covering permissions, network activity, malware, and exfiltration behaviors across Mozilla's add-ons directory.
Scans every Firefox extension listed in Mozilla's official add-ons directory, monitoring new releases for changes in permissions, code, network activity, and behavior. Not checked yet Detects malware, credential and clipboard theft, data exfiltration data exfiltration Moving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels. , remote loading, obfuscation, impersonation, and related campaign activity in Firefox extensions. Not checked yet Firefox extension coverage is available in Experimental for Enterprise customers — contact your Socket account team to enable it. Not checked yet
3 details in Everything
Socket adds experimental Firefox extension protection scanning for enterprise customers
Adds support for scanning Firefox extensions listed in Mozilla's official add-ons directory. Not checked yet Enables monitoring of new Firefox extension releases for changes in permissions, code, network activity, and behavior. Not checked yet
2 details in Everything
Socket splits legacy Alert Triage into two new APIs: policy rules and alert resolutions, each with distinct endpoints and selectors.
└──▷ TRY IT
Migrate a legacy pattern rule that monitored unreachable critical CVEs in lodash 4.x to a new policy rule.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{
"name": "Monitor unreachable critical CVEs in lodash 4.x",
"action": "monitor",
"note": "Unreachable in our services",
"position": "last",
"vigil_selector": {
"finding.alertType": "criticalCVE",
"finding.cvss": { "$gte": 7.5 },
"finding.reachability": "unreachable",
"artifact.type": "npm",
"artifact.name": "lodash",
"artifact.version": { "$prefix": "4." }
}
}' \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/default/rules
Migrate a legacy single-finding suppression to an alert resolution scoped to a specific CVE, repo, and exact package version.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{
"reason": "tolerable_risk",
"comment": "Dev-only dependency, not shipped",
"vigil_selector": {
"finding.alertType": "criticalCVE",
"finding.cveId": "CVE-2024-29041",
"location.repo": "my-org/internal-tools",
"artifact.type": "npm",
"artifact.name": "lodash",
"artifact.version": "4.17.20"
}
}' \
https://api.socket.dev/v0/orgs/$ORG/alerts/resolutions
Adds POST /orgs/{org_slug}/alert-policies/default/rules to create policy rules with vigil_selector, action, note, and placement controls (position, before_rule_id, after_rule_id, or rank). Not checked yet Adds GET .../rules returning { "items": [...] } in evaluation order, PUT .../rules/{rule_id} for partial-update and rule reordering, and DELETE .../rules/{rule_id} for removal. Not checked yet Adds POST /orgs/{org_slug}/alerts/resolutions to create alert resolutions scoped by vigil_selector fields including finding.cveId, finding.ghsaId, location.repo, artifact.version, with optional reason, comment (up to 1024 chars), and reason_text (up to 256 chars). Not checked yet Adds GET /orgs/{org_slug}/alerts/resolutions with cursor pagination via startAfterCursor and endCursor, plus per_page (1–100, default 30) and direction; DELETE .../resolutions/{uuid} restores hidden alerts on next refresh. Not checked yet New vigil_selector operator support includes $prefix for version-range matching (e.g. { "$prefix": "4." }), $gte for CVSS CVSS Common Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. score thresholds, $in for multi-value reachability states, and $or for matching either finding.cveId or finding.ghsaId. Not checked yet
+3 more
show less
Maps legacy state values to new action values: block → error, warn → warn, monitor → monitor, ignore → ignore; inherit requires no rule. Not checked yet Maps legacy matcher fields to new selector fields: packageType → artifact.type, packageNamespace → artifact.namespace, packageName → artifact.name, packageVersion → artifact.version, alertType → finding.alertType, cvssScoreCmp → finding.cvss, cveOrGhsaId → finding.cveId/finding.ghsaId, fixAvailable → finding.fixAvailable, kevs → finding.hasKEV, reachability → finding.reachability. Not checked yet Introduces finding.cvePatchStatus selector field to query whether a Socket patch exists or is applied for a finding — distinct from the legacy patchAvailable entitlement check, which has no direct translation. Not checked yet
8 details in Everything
└──▷ BREAKING ON UPGRADE
! The legacy POST /orgs/{org_slug}/triage/alerts batch API (keyed under alertTriage) and DELETE /orgs/{org_slug}/triage/alerts/{uuid} are replaced by separate policy-rule and alert-resolution endpoints; existing integrations must migrate.! The legacy patchAvailable field has no equivalent in the new API and does not translate — rules relying on it must be rewritten using finding.fixAvailable and/or finding.cvePatchStatus.! Legacy entries carrying an alertKey (suppressing one specific alert instance) have no vigil_selector equivalent and must be recreated as alert resolutions scoped to repo, package, version, and alert type.
Socket replaces the legacy Security Policy API with a baseline-preset plus explicit rules model, exposing new policy and rule endpoints.
└──▷ TRY IT
Migrate a legacy policy that blocks critical CVEs by setting the balanced baseline on the default policy, then adding a per-alert-type override rule.
copy
$ curl -u "$SOCKET_API_TOKEN:" -X PUT \
-H "Content-Type: application/json" \
-d '{ "baseline": "balanced" }' \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/default
curl -u "$SOCKET_API_TOKEN:" -X POST \
-H "Content-Type: application/json" \
-d '{
"name": "Block critical CVEs",
"action": "error",
"vigil_selector": { "finding.alertType": "criticalCVE" }
}' \
https://api.socket.dev/v0/orgs/$ORG/alert-policies/default/rules
Inspect the full equivalent of the legacy security policy GET by reading the default policy baseline and its rules in evaluation order.
copy
$ curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alert-policies
curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alert-policies/default/rules
Adds GET /orgs/{org_slug}/alert-policies to list all policies, returning the default policy first followed by custom policies in creation order. Not checked yet Adds GET /orgs/{org_slug}/alert-policies/{policy_id}/rules returning { "items": [ ... ] } in evaluation order, replacing the single-response legacy GET. Not checked yet Adds PUT /orgs/{org_slug}/alert-policies/{policy_id} accepting name, description, repository_ids, and baseline fields; only sent fields are updated, and repository_ids replaces the entire set. Not checked yet Adds POST /orgs/{org_slug}/alert-policies/{policy_id}/rules to create per-alert-type rules with a name, action, and vigil_selector (e.g. { "finding.alertType": "criticalCVE" }); returns 201 with the stored rule including its full selector and rank. Not checked yet Adds DELETE on a policy, which removes the policy, its rules, and its label; repositories assigned to it fall back to the default policy. The default policy cannot be renamed or deleted. Not checked yet
+2 more
show less
The default policy is addressable as the literal string default as policy_id in every policy and rule endpoint, even after it is first modified and receives a UUID UUID A universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide. . Not checked yet New policy model introduces a baseline preset field per policy, replacing the organization-wide securityPolicyDefault; actions error, warn, monitor, ignore, and defer carry over, with defer now meaning fall back to the baseline preset. Not checked yet
7 details in Everything
Socket adds new alert-policies and alert-resolutions REST API REST API A web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. endpoints, replacing legacy security-policy and triage endpoints.
└──▷ TRY IT
List all alert policies for your org using the new endpoint and an org-scoped API token, as a drop-in replacement for the legacy security-policy GET.
copy
$ curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alert-policies
List all alert resolutions (specific suppressed findings) for your org — a capability that had no dedicated legacy endpoint.
copy
$ curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alerts/resolutions
Introduces GET /orgs/{org_slug}/alert-policies and GET /orgs/{org_slug}/alert-policies/{policy_id}/rules as replacements for GET /orgs/{org_slug}/settings/security-policy. Not checked yet Introduces POST /orgs/{org_slug}/alert-policies, PUT /orgs/{org_slug}/alert-policies/{policy_id}, and rule endpoints as replacements for POST /orgs/{org_slug}/settings/security-policy. Not checked yet Introduces GET /orgs/{org_slug}/alerts/resolutions, POST /orgs/{org_slug}/alerts/resolutions, and DELETE /orgs/{org_slug}/alerts/resolutions/{uuid} to handle specific finding suppressions previously mixed into POST /orgs/{org_slug}/triage/alerts. Not checked yet Introduces GET /orgs/{org_slug}/alert-policies/{policy_id}/rules, POST /orgs/{org_slug}/alert-policies/{policy_id}/rules, and DELETE /orgs/{org_slug}/alert-policies/{policy_id}/rules/{rule_id} as replacements for the legacy triage endpoints. Not checked yet Adds net-new GET, PUT, and DELETE on /orgs/{org_slug}/alert-policies/{policy_id} and on individual rules — endpoints with no legacy equivalent. Not checked yet
+2 more
show less
Introduces fine-grained token scopes for the new endpoints: alert-policy:list, alert-policy:read, alert-policy:create, alert-policy:update, alert-policy:delete for policies and rules; alert-resolution:list, alert-resolution:read, alert-resolution:create, alert-resolution:delete for resolutions. Not checked yet Alert resolution endpoints are accessible to repository-restricted tokens within their granted repositories, while all alert-policy endpoints require organization-wide repository access (repository-restricted tokens receive 403). Not checked yet
7 details in Everything
└──▷ BREAKING ON UPGRADE
! Once an organization's migration window ends (30 days from when migration is enabled), the legacy POST /orgs/{org_slug}/settings/security-policy and POST /orgs/{org_slug}/triage/alerts endpoints stop accepting writes — automation must be updated to the new endpoints before the cutover.
Socket introduces Policies: ordered alert-action rules with baseline presets, per-repo scoping, and full REST API REST API A web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. management.
Adds a Policies system where each policy is an ordered list of rules that assigns one of four actions — error (Block), warn, monitor, or ignore — to every alert Socket raises. Not checked yet Introduces four baseline presets (Essential , Balanced , Comprehensive , None ) that sit beneath custom rules, with Balanced as the default for new policies and the Default policy. Not checked yet Supports per-repository policy scoping: each repository belongs to exactly one policy, and the Default policy governs any repository not explicitly assigned to another. Not checked yet Exposes full policy management via the Socket REST API using Vigil selectors — covering list, create, get, update, and delete operations for both policies and individual rules. Not checked yet Adds Drafting Rules with AI capability: describe rules in plain language and review Socket-generated rule drafts before applying them. Not checked yet
+1 more
show less
Adds a Migrating to Policies guide for moving existing Socket configurations to the new Policies system. Not checked yet
6 details in Everything
Repository-Scoped API Tokens Now Support Reachability Scans (2026-07-09)
Jul 9, 2026
· release notes
Socket adds reachability scan file listing support to repository-scoped API tokens
Repository-scoped API tokens can now retrieve the supported-files list required to start reachability scans Not checked yet
1 detail in Everything
Packagist Package Pages Now Surface Force-Pushed Tags (2026-07-06)
Jul 6, 2026
·
issue 014
Socket now surfaces full commit history for force-pushed Packagist tags, highlighting the current and prior commits.
Displays full commit history for force-pushed tags on Packagist package pages, with the currently associated commit highlighted. Not checked yet Enables review of commits a package version previously referenced before a tag was overwritten. Not checked yet
2 details in Everything
Private Package Scores Now Display as N/A (2026-07-03)
Jul 3, 2026
· release notes
Socket now displays N/A for unscoreable private package scores in PR comments and dependency views
Private packages that Socket cannot score now display N/A instead of a numeric score in pull request comments and dependency views. Not checked yet
1 detail in Everything
New: AI-Reviewed Reachability Specifications (2026-06-30)
Jun 30, 2026
·
issue 014
Socket adds opt-in AI-generated reachability specs to expand vulnerability reachability coverage beyond human-verified rules.
└──▷ HOW TO FIND IT
Enable AI-generated reachability specs org-wide to get reachability verdicts on a broader set of vulnerabilities during alert scans.
📍 In the console, go to Settings → Alert Scans → Reachability and enable the AI-generated reachability specifications option.
Adds opt-in AI-reviewed reachability specifications that extend reachability verdicts to vulnerabilities not yet covered by human-verified specs. Not checked yet New Specification field in alert details surfaces whether a reachability result was produced by an AI-generated or human-verified specification. Not checked yet
2 details in Everything
New: AI-Reviewed Reachability Specifications
Jun 30, 2026
· release notes
Socket adds opt-in AI-generated reachability specifications and a Specification field in alert details to broaden coverage.
Adds Settings → Alert Scans → Reachability toggle to enable AI-generated reachability specifications alongside human-verified ones Not checked yet Adds a Specification field to Alert details showing whether the reachability result came from an AI-generated or human-verified specification Not checked yet
2 details in Everything
Redesigned Organization Switcher for Faster Navigation (2026-06-29)
Jun 29, 2026
·
issue 014
Socket's organization switcher now surfaces Settings and orgs upfront, with a searchable All Organizations view.
└──▷ HOW TO FIND IT
Quickly jump between organizations when managing multiple clients or teams.
📍 In the Socket console, click the organization switcher in the top navigation, then type an organization name in the All Organizations search box to filter and select it instantly.
Redesigned organization switcher surfaces Settings and organizations at the top level for faster access. Not checked yet New searchable All Organizations view for users belonging to multiple organizations. Not checked yet
2 details in Everything
Redesigned Organization Switcher for Faster Navigation
Jun 29, 2026
· release notes
Redesigned Organization Switcher now includes a searchable All organizations view for faster navigation.
Adds a searchable All organizations view in the Organization Switcher for users with multiple organizations Not checked yet Surfaces Settings and organization list up front in the redesigned switcher UI Not checked yet
2 details in Everything
Alert Titles Added to CSV Exports (2026-06-23)
Jun 23, 2026
·
issue 014
Socket CSV exports now include a human-readable Alert Title column and more consistent Upgrade Version values.
Adds a human-readable Alert Title column to Alerts CSV exports, enabling direct CVE identification without cross-referencing the dashboard. Not checked yet Populates Upgrade Version values more consistently in vulnerability alert CSV exports. Not checked yet
2 details in Everything
Socket adds an Alert Title column to CSV exports for easier CVE identification.
CSV exports now include a human-readable Alert Title column for vulnerability alerts Not checked yet
1 detail in Everything
Socket MCP adds organization alerts, threat feed, and package inspection
Jun 18, 2026
· release notes
Socket MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. adds org alerts, threat feed querying, and authenticated package inspection
Adds organization-level alert review with filtering by severity or repository Not checked yet Enables querying the Socket threat feed by ecosystem, category, and time window Not checked yet Allows listing, reading, and searching published package artifacts without local installation Not checked yet Connects package findings to affected repositories and organization alerts Not checked yet Supports authentication for org alerts and threat feed; depscore remains public Not checked yet
5 details in Everything
New: Socket Firewall support for VS Code and Open VSX
Jun 17, 2026
· release notes
Socket Firewall now filters and blocks flagged VS Code/Open VSX Open VSX An open-source registry for VS Code extensions, maintained by the Eclipse Foundation, giving cyber tools a vendor-neutral alternative to the proprietary Microsoft Marketplace for distributing editor plugins. extensions via marketplace proxying.
Adds Socket Firewall support for VS Code and Open VSX to filter flagged extensions from marketplace results. Not checked yet Enables blocking at extension asset and VSIX download URLs in the Socket Firewall closed beta. Not checked yet Supports deployment through editor configuration, DNS override, or enterprise egress forwarding. Not checked yet
3 details in Everything
New: Manifest Alerts for missing lockfiles
Jun 16, 2026
· release notes
Socket introduces Manifest Alerts for missing lockfiles with Jira/Linear integration
Adds Manifest Alerts view to scan results for detecting missing lockfiles in application and project repositories Not checked yet Supports impact details and remediation for npm, pnpm, yarn, and bun ecosystems when a manifest lacks a corresponding lockfile Not checked yet Adds controls to ignore/restore Manifest Alerts and create Jira or Linear tickets directly from the alert Not checked yet
3 details in Everything
Add Firewall events data export (2026-06-16)
Jun 16, 2026
·
issue 014
Socket Firewall now supports exporting event logs to external data sources via the new Data Export integration.
└──▷ HOW TO FIND IT
Route Firewall event logs to an external SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. or data pipeline for retention and analysis.
📍 In the console, go to Settings › Data Export › Create Integration, then select Telemetry events as the data type.
Socket adds UI step to export Firewall telemetry event logs to external integrations
Adds UI path Settings > Data Export > Create Integration for exporting Socket Firewall telemetry events Not checked yet
1 detail in Everything
Obfuscated Code Alerts Now Default to Monitor
Jun 16, 2026
· release notes
Socket changes default standalone obfuscated code alerts to Monitor instead of Warn.
Packagist Package Pages Now Show Daily Download Trends
Jun 14, 2026
· release notes
Packagist package pages now display a daily downloads chart powered by Packagist stats.
Crates Package Pages Now Show Daily Download Trends
Jun 13, 2026
· release notes
Socket crates.io package pages now display daily download metrics and trend graphs.
Crates package pages on Socket.dev now include daily download metrics sourced from crates.io Not checked yet Daily download trends visualization is added to crate package pages for adoption analysis Not checked yet
2 details in Everything
Bulk-Assign Repository Labels with CSV Import
Jun 6, 2026
· release notes
New CSV import feature for bulk-assiging repository labels in Socket
Adds CSV import capability to the Repositories → Labels page for bulk label assignment Not checked yet
1 detail in Everything
Surface Go retraction and PyPI yank warnings
Jun 4, 2026
· release notes
Socket updates its UI to highlight risky package versions in Go and PyPI repositories.
Adds a warning banner on Go and PyPI package pages when a version is retracted or yanked Not checked yet
1 detail in Everything
Surface package keywords for GitHub Actions and Packagist
Jun 3, 2026
· release notes
Socket displays package keywords and marketplace categories for GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. and Packagist packages.
Composer package pages now show a Homepage link when available.
Show OpenVSX publishers and repository links
May 31, 2026
· release notes
OpenVSX package pages now display publisher info and source repository links
Adds publisher name to the maintainers view and overview metadata for OpenVSX package pages Not checked yet
1 detail in Everything
Add OpenVSX categories, compatibility, and homepage metadata
May 31, 2026
· release notes
Socket now displays OpenVSX categories, compatibility, and homepage metadata on package pages.
OpenVSX extension categories are now visible on Socket package pages Not checked yet VS Code version compatibility information is displayed for OpenVSX extensions Not checked yet Homepage links are shown for OpenVSX extensions when available Not checked yet
3 details in Everything
Surface Chrome Web Store user counts
May 29, 2026
· release notes
Socket Surface now displays Chrome Web Store active-user counts on extension package pages, separating them from download metrics to aid popularity evaluation.
Add duplicate redirect support to diff scan creation
May 21, 2026
· release notes
Adds on_duplicate=redirect support to POST /v0/orgs/{org_slug}/diff-scans/from-ids for handling duplicate scans
Add relative date filters to Vulnerabilities and Scans
May 19, 2026
· release notes
Adds relative date filters (e.g., 1 week ago ) to Vulnerabilities and Scans pages in Socket UI.
Supports relative date presets like 1 week ago and 1 month ago on Vulnerabilities and Scans pages Not checked yet Adds a Detected date filter specifically for the Vulnerabilities page Not checked yet Adds created-date filtering with custom calendar options and before/after operators to the Scans page Not checked yet
3 details in Everything
Campaign pages now show artifact identifiers
May 15, 2026
· release notes
Campaign pages now display artifact identifiers for affected packages to distinguish identical versioned distributions.
Adds artifact identifiers (e.g., PyPI wheel tags, Maven jar qualifiers) to campaign pages under each affected package. Not checked yet
1 detail in Everything
Add html_url to repository API responses
May 1, 2026
· release notes
Repository API responses now include html_url pointing to the Socket dashboard.
Add security policy confirmations and JSON copy actions in the dashboard
Apr 30, 2026
· release notes
Adds security policy confirmations and Copy JSON button in the dashboard
Security Policy now requires confirmation before removing custom alert settings or switching presets when custom overrides are present. Not checked yet Firewall event details include a Copy JSON button to copy the full event body. Not checked yet
2 details in Everything
Add Security settings for active sessions
Apr 30, 2026
· release notes
Socket introduces a Security tab within User Preferences for managing active user sessions.
Adds a new Security tab in the User Preferences UI to view and terminate active account sessions Not checked yet
1 detail in Everything
Added Gradle Version Catalog Support for SBOM Generation
Apr 11, 2026
· release notes
Socket adds Gradle Version Catalog (libs.versions.toml) support for SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation fallback.
Adds parsing of libs.versions.toml files during SBOM generation to improve dependency detection for Gradle projects without lockfiles. Not checked yet
1 detail in Everything
Updated Default Policy Settings for AI-Detected Potential Malware
Apr 3, 2026
· release notes
Socket updates default actions for AI-detected potential malware alerts to warn across all policies, with future block capability.
Sets the default action for AI-detected potential malware alerts to warn in low noise, default, and higher noise security policies Not checked yet
1 detail in Everything
Added Markdown Rendering for Supply Chain Attack Descriptions
Mar 27, 2026
· release notes
Adds Markdown rendering to Supply Chain Supply Chain The network of vendors, dependencies, and build processes that produce and deliver software; cyber tools target it because a compromise anywhere upstream can silently backdoor every downstream consumer. Attack Descriptions in public and dashboard views.
Sync Individual GitHub Installations
Mar 26, 2026
· release notes
Adds ability to sync individual GitHub app installations from Dashboard UI and clarifies global sync scope.
Adds UI option to sync a single GitHub installation via Dashboard → Integrations → GitHub Not checked yet Clarifies that the Sync all GitHub installations button syncs every linked organization installation Not checked yet
2 details in Everything
Socket API now includes scan scores in streaming events and supports detailed score breakdowns via query parameter
Streaming full-scan data now includes a scores event type containing score details Not checked yet Adds ?include_score_details query parameter to view components of full-scan scores Not checked yet
2 details in Everything
Improved Mobile Experience for Attack Campaign Pages
Mar 24, 2026
· release notes
Improved mobile usability for public supply chain attack campaign pages.
Improved Package Search Result Display in the Overlay
Mar 5, 2026
· release notes
Improved package search overlay behavior with conditional View all and accurate footer counts.
The package search overlay now shows the View all option only when more than 20 results are available. Not checked yet The result list behaves more consistently when exact matches or empty states are shown. Not checked yet
2 details in Everything
Preserved File Paths When Switching Package Versions and Artifacts
Mar 2, 2026
· release notes
Package file navigation preserves current path when switching versions or artifacts
Fixed Empty Workspace Parameter Handling for Repository Scans
Feb 27, 2026
· release notes
Socket fixes workspace parameter handling to allow omitting or passing an empty value for default workspace scans
Omitting the workspace parameter now correctly targets the default-workspace repository for full or diff scans Not checked yet
1 detail in Everything
New: “Summarize With AI” Links to Blog Posts
Feb 26, 2026
· release notes
Socket adds Summarize With AI links to blog posts for quick TL;DR via external AI assistants.
Added Generic Bucket Export Integration
Feb 14, 2026
· release notes
Socket adds generic bucket export integration supporting AWS S3, GCS, Azure Blob with CSV/JSON/Parquet formats.
Adds aws_s3 bucket support for generic alert data export Not checked yet Adds google_cloud_storage (GCS) bucket support for generic alert data export Not checked yet Adds azure_blob_storage bucket support for generic alert data export Not checked yet Adds csv, json, and parquet output format support for bucket exports Not checked yet
4 details in Everything
Display Scan Type Indicator On SBOM Report Page
Feb 14, 2026
· release notes
SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. report pages now display a scan type indicator in the header.
New: Scan Type Column And Filtering In Full Scans
Feb 13, 2026
· release notes
New Scan Type column and filtering in Full Scans UI and API to distinguish socket, tier1, or basics scans.
New Triage Page in Organization Settings
Feb 5, 2026
· release notes
Socket introduces a centralized UI for organization-level triage policy management.
The new Triage page consolidates visibility of PURL PURL A Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously. -based and Alert Key-based rules. Not checked yet
1 detail in Everything
Universal PURL Redirect for Package Pages
Feb 3, 2026
· release notes
Adds https://socket.dev/purl/<purl> endpoint for universal package page redirects
Adds a new standardized PURL PURL A Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously. -based redirect endpoint at /purl/$URL_ENCODED_PURL that routes to the correct package page regardless of ecosystem Not checked yet
1 detail in Everything
Socket Alert Triage API gains required ?force parameter and DELETE support.
Adds ?force query parameter to the Alert Triage API to require confirmation for broad triage operations Not checked yet Adds DELETE method support to the Alert Triage API to remove previously applied triage Not checked yet
2 details in Everything
Improved Alert Details With Associated Files
Jan 26, 2026
· release notes
Improved Alert Details With Associated Files
New: Configurable Display Options for Alert Tables
Jan 15, 2026
· release notes
Socket adds configurable display options for alert table badges via a new UI menu
Customizable Alert Table Badges and Display Options
Jan 15, 2026
· release notes
Alert table supports configurable display options for grouping and badge ordering.
Adds configurable display options to alert tables, allowing users to control how alerts are grouped and which badges (e.g., priority, severity, action) appear first. Not checked yet
1 detail in Everything
More Flexible Alert Table Display Options
Jan 15, 2026
· release notes
Socket adds configurable badge display options for dashboard alert tables
Socket CLI 1.1.58 adds --reach-enable-analysis-splitting to control analysis splitting for reachability scans.
Adds --reach-enable-analysis-splitting flag to opt-in to multiple analysis runs per workspace for reachability scans Not checked yet Analysis splitting is now disabled by default for reachability scans Not checked yet
2 details in Everything
New: Organization-Scoped PURL Endpoint
Jan 8, 2026
· release notes
Socket adds POST /v0/orgs/{org_slug}/purl endpoint for organization-specific policy application
Adds POST /v0/orgs/{org_slug}/purl endpoint to apply organization-specific policies based on repository labels Not checked yet Deprecates POST /v0/purl legacy endpoint, scheduled for removal on 2026-07-30 Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! The POST /v0/purl endpoint is deprecated and will be removed on 2026-07-30, requiring migration to POST /v0/orgs/{org_slug}/purl
New: Wildcard Scope Support for API Tokens
Jan 8, 2026
· release notes
API tokens now support a wildcard [*] scope to automatically inherit all future scopes.
PublishedAt Field Added to Threat Feed API
Jan 7, 2026
· release notes
Threat Feed API adds publishedAt field to result objects
Adds publishedAt field to Threat Feed API responses (ISO 8601 ISO 8601 An international standard for representing dates and times as text, using formats like 2025-04-23T14:00:00Z. Tools adopt it to ensure timestamps are unambiguous and sortable across systems and locales. or null) Not checked yet Exposes new timestamp in GET /v0/orgs/{org_slug}/threat-feed endpoint Not checked yet
2 details in Everything
Python CLI: Slack Bot Mode Support Added
Jan 5, 2026
· release notes
Socket Python CLI adds Slack bot mode for multi-channel alerting
Adds Slack bot mode to the Socket Python CLI alongside existing webhook-based notifications Not checked yet Enables posting alerts to multiple Slack channels using a bot token Not checked yet Supports configurable filters per channel Not checked yet Supports reachability alerts during full scans Not checked yet
4 details in Everything
Swift package pages now surface source repo metadata like avatar, issues, PRs, archive status, and stars.
Swift package pages now link to the source repository Not checked yet Surface related GitHub metadata including repository avatar, open issues, pull requests, archived or disabled status, and stargazer reputation Not checked yet
2 details in Everything
Socket CLI 1.1.52 updates the internal Coana CLI engine.
Python CLI: Slack Formatter Added for Reachability Analysis
Jan 3, 2026
· release notes
Socket Python CLI now supports Slack notifications with reachability-prioritized formatting for Socket Facts.
Slack formatter prioritizes reachable vulnerabilities and respects Slack block size limits Not checked yet
1 detail in Everything
Python SDK: Custom User Agent Support
Jan 2, 2026
· release notes
Socket Python SDK adds custom User Agent support for library users
Adds the ability to override the default User Agent string in the Socket Python SDK. Not checked yet
1 detail in Everything
Python SDK: Expanded Endpoint Coverage and Enhancements
Jan 2, 2026
· release notes
Socket Python SDK gains OpenVEX OpenVEX An open specification and Go library, maintained by the OpenVEX community, for expressing VEX (Vulnerability Exploitability eXchange) statements in a standard JSON format so cyber tools can automate vulnerability triage. export, archive support, and env var token auth
Adds openvex_bom method for exporting Software Bill of Materials Software Bill of Materials A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. in OpenVEX format Not checked yet Adds support for initializing API tokens via environment variables instead of only constructor arguments Not checked yet Adds new endpoint modules for Alerts, full scan search, Fixes, Supported Files, Webhooks, and Telemetry to the Socket API Not checked yet Adds archive upload support for .tar, .tar.gz, .tgz, and .zip files Not checked yet Adds lazy file loading for improved performance when scanning large workspaces Not checked yet
+2 more
show less
Adds full scan rescan support and archive download capabilities Not checked yet Adds dependencies_trend method for dependency history analysis Not checked yet
7 details in Everything
Socket adds SHA-512 SHA-512 A cryptographic hash function in the SHA-2 family, standardized by NIST, that produces a 512-bit digest. Cyber tools use it for integrity verification and password hashing where collision resistance matters. hash-based operations for API tokens to reduce exposure in logs and requests.
sha512- SRI format hashes are now included with newly created or rotated API tokens Not checked yet API endpoints now accept token hashes for rotation, update, and revocation operations Not checked yet
2 details in Everything
Socket CLI 1.1.47 adds a --debug flag to socket fix for verbose logging.
Adds Contributor-level access to the organization's Dependencies tab in Socket UI.
New Webhook Testing and Debugging view in Socket for inspecting delivery logs
Adds a new Debug Webhook view showing a paginated table of sent messages with detailed request/response delivery logs Not checked yet
1 detail in Everything
Adds --reach-use-only-pregenerated-sboms to restrict reachability analysis to pre-computed SBOMs SBOMs A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue.
Adds --reach-use-only-pregenerated-sboms flag to run Tier 1 reachability using only pre-computed CDX and SPDX SPDX An open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format. SBOMs Not checked yet Updated the Coana CLI dependency to v 14.12.122 Not checked yet
2 details in Everything
New Campaigns Tab on the Threat Intel Page
Dec 8, 2025
· release notes
New Campaigns tab on Threat Intel page adds supply chain attack visibility
Expands the logged-in dashboard Threat Feed with an Insights panel Not checked yet Introduces a dedicated campaign detail page linking back to impacted repositories in your dashboard Not checked yet
2 details in Everything
Socket CLI 1.1.43 adds --all flag to process all vulnerabilities in local mode
Create Full Scans from the Dashboard via Manifest Uploads
Dec 5, 2025
· release notes
Dashboard allows full scans via manifest file upload for CI-free testing
Adds ability to create a full scan from the Socket dashboard by uploading manifest files Not checked yet
1 detail in Everything
Socket CLI 1.1.41 adds --reach-version and --fix-version flags to override @coana-tech/cli versions
Socket CLI 1.1.39 introduces a file output capability for the socket scan reach command via the --output flag and updates its underlying Coana CLI engine.
socket scan reach now supports the --output <path> flag (e.g., --output scan-report.json) to write the scan result to a file Not checked yet
1 detail in Everything
Socket CLI 1.1.35 adds --reach-debug for verbose reachability logging
New: Webhook Events for Alert Changes
Nov 22, 2025
· release notes
Socket adds real-time webhook events for alert lifecycle changes (create, update, clear)
Adds socket webhook events that fire when an alert is created, updated, or cleared across repositories Not checked yet
1 detail in Everything
Org-level telemetry configuration via API endpoints and dashboard settings
Adds GET /api/telemetry and PUT /api/telemetry endpoints to retrieve and update org-level telemetry settings Not checked yet Introduces a new dashboard settings page for admins and owners to enable or disable telemetry at the organization level Not checked yet
2 details in Everything
Socket adds experimental scanning for OpenVSX extensions to surface supply chain threats in developer tools
Add Search to the Package File Explorer
Nov 21, 2025
· release notes
Adds search capability to the Package File Explorer in Socket's UI.
Socket adds beta coverage for Bun and vlt package managers
Adds bun.lock and vlt-lock.json file detection to automatically analyze dependency graphs for Bun and vlt projects Not checked yet
1 detail in Everything
Socket adds function-level reachability analysis for Ruby in beta to identify exploitable vulnerabilities.
Socket API v0 gains full CRUD CRUD The four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information. endpoints for programmatic webhook management
Adds create, get, list, update, and delete API endpoints for managing webhooks in Socket API v0 Not checked yet
1 detail in Everything
Socket adds full SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation from vlt lockfiles (vlt-lock.json) with workspace, git, and file dependency support.
Adds vlt arborist integration for accurate dependency resolution from vlt-lock.json Not checked yet Enables full SBOM output pipeline for vlt projects including workspaces, git dependencies, and file dependencies Not checked yet
2 details in Everything
Socket CLI 1.1.29 adds concurrency and analysis splitting controls for socket scan create --reach.
Python CLI: New Reachability Flag and Improved Docker Entrypoint
Nov 16, 2025
· release notes
The Socket Python CLI now allows disabling analysis splitting for reachability scans via a new flag, and fixes Docker entrypoint compatibility.
Add Option to Disable SSL Verification in Python SDK
Nov 14, 2025
· release notes
Socket Python SDK gains allow_unverified parameter in constructor to skip SSL SSL A cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. verification
Adds allow_unverified optional parameter to the socketdev constructor to disable SSL certificate verification Not checked yet
1 detail in Everything
Improve Reachability Analysis Options and SSL Handling in Python CLI
Nov 14, 2025
· release notes
Socket CLI adds --reach-concurrency and --reach-additional-params flags and fixes SSL SSL A cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. verification.
Added --reach-concurrency flag to control parallel execution in reachability analysis (minimum value: 1) Not checked yet Added --reach-additional-params flag to pass custom parameters to the coana CLI tool Not checked yet
2 details in Everything
Add Optional Summary Parameter to Batch PURL Endpoint
Nov 14, 2025
· release notes
Socket's /v0/purl batch endpoint adds optional summary=true parameter for batch resolution counts
Socket CLI v1.1.27 enables selective package remediation by adding --exclude and --include arguments to the socket fix command, mirroring functionality available in v2.
--exclude flag added to socket fix. Not checked yet
1 detail in Everything
Restore Settings for Disabling Ecosystems on the Alerts Scans Page
Nov 12, 2025
· release notes
Socket adds UI toggles on Settings > Alerts > Scans to control which ecosystems are scanned for alerts
Adds debug logging for API requests and responses in Socket CLI 1.1.26
Socket Python CLI Docker image now includes uv for reliable Coana reachability analysis.
Python CLI: Reachability Analysis Support
Nov 7, 2025
· release notes
Socket CLI adds --reach for dependency reachability analysis to filter non-exploitable vulnerabilities
Adds the --reach flag to enable reachability analysis of vulnerable dependencies Not checked yet Adds the --only-facts-file flag to submit reachability results independently Not checked yet
2 details in Everything
License Policy API Now Includes 'deny' Field
Nov 1, 2025
· release notes
License Policy API now exposes a deny field in responses and exports to list all unallowed licenses.
deny field added to JSON exports of license policies Not checked yet
1 detail in Everything
Added Support for TypeScript Declaration File Extensions
Oct 29, 2025
· release notes
Package diff viewer adds support for TypeScript and JavaScript declaration file extensions
Adds CSV export capability to the Scans view (SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. Report Page)
CSV Export to Scans View Not checked yet
1 detail in Everything
Socket Firewall Enterprise adds on-prem HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. proxy deployment, org-wide policy controls, and multi-ecosystem support.
Adds Socket Firewall Enterprise edition with flexible deployment options including long-lived HTTPS proxy for on-prem environments Not checked yet Adds configurable organization-wide policies to customize which alerts trigger warnings or blocks via integration with Socket's security and license policies Not checked yet Adds support for Maven, Go modules, RubyGems, and NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. package ecosystems alongside existing JavaScript, Python, and Rust coverage Not checked yet Introduces MUSL build for improved compatibility with CI pipelines and containerized deployments Not checked yet
4 details in Everything
New: GitHub Actions Scanning Support
Oct 23, 2025
· release notes
Socket adds experimental scanning of GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. workflows for security and license risks.
Supports scanning GitHub Actions workflows for security and license risks via deep package inspection Not checked yet Detects malicious or obfuscated code in action dependencies using the Argus taint-tracking engine Not checked yet
2 details in Everything
New: Webhook Events for Pull Request Scans
Oct 23, 2025
· release notes
Socket adds webhook events for pull request scans to push results directly to Slack, Jira, or CI pipelines.
Adds Webhook Events for Pull Request Scans, allowing automatic receipt of scan results and security alerts in real time. Not checked yet Webhook payloads include detailed information about changed dependencies, new alerts, and direct links to the Socket dashboard and API. Not checked yet
2 details in Everything
Socket launches Basics to unify SAST SAST Static application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. , secret detection, container scanning, CVE checks, and policy management via Dashboard.
Unifies Static analysis (SAST) for 14 programming languages, Secrets detection, Container/Dockerfile scanning, and CVE scanning under one workflow Not checked yet Centralizes policy management through the Socket Dashboard Not checked yet
2 details in Everything
Expanded: Socket Basics Configuration
Oct 21, 2025
· release notes
Socket Basics expands configuration options for SAST SAST Static application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. , secrets, and notifications with UI updates
Adds over 100 new configuration options for Socket Basics to control security scanning settings Not checked yet Supports per-language rule customization across 17 language SAST scanners Not checked yet Enables secret and container scanning configuration via expanded config keys Not checked yet Adds Socket Tier 1 reachability analysis controls in the configuration Not checked yet Integrates 12 notification channels (Slack, Jira, GitHub, Microsoft Teams) via config settings Not checked yet
+1 more
show less
Redesigns the UI with organized sections and an All Languages toggle Not checked yet
6 details in Everything
Added: Critical Alert Priority and Colorful Priority Icons
Oct 21, 2025
· release notes
Socket introduces a new critical alert priority level and updates UI icons to be color-coded for better visibility.
Introduces critical as a new alert priority level alongside high, medium, and low. Not checked yet Renders priority icons with color-coding for easier scanning in the UI. Not checked yet
2 details in Everything
Experimental Malware Scanning for Hugging Face Models
Oct 21, 2025
· release notes
Socket introduces experimental supply chain protection for AI models, allowing users to detect hidden payloads in major frameworks and integrate scanning via API or AIBOM AIBOM An inventory of every AI model, dataset, and dependency used in a system, analogous to a software bill of materials, giving cyber tools a structured way to audit AI supply-chain risk. .
Socket Firewall v0.14.0 adds configurable action for unrecognized hostnames and graceful API retry handling
action configuration added to control the default network behavior for unrecognized hostnames. Not checked yet Graceful retry handling introduced for failed API calls or non-2xx responses. Not checked yet
2 details in Everything
Socket CLI 1.1.24–1.1.25 adds flags to control dependency update scope and support local analysis.
Adds --minimum-release-age flag for the socket fix command to skip fixes for recently released dependencies Not checked yet Supports SOCKET_CLI_COANA_LOCAL_PATH environment variable to configure local Coana analysis paths Not checked yet Adds --no-major-updates flag to prevent major version upgrades during remediation Not checked yet Adds --show-affected-direct-dependencies flag to display direct dependencies impacted by a fix Not checked yet
4 details in Everything
New: Support for Python Vulnerability Fixes in socket fix
Oct 8, 2025
· release notes
socket fix now auto-upgrades affected Python dependencies in requirements.txt and uv.lock uv.lock A machine-generated lockfile produced by uv, Astral's Python package manager, that pins every dependency to an exact version and hash so builds are perfectly reproducible across machines. .
Adds custom tabs in org alerts to save, name, and share filter sets across the organization.
Adds the ability to create, rename, duplicate, and delete custom tabs on the org alerts page for business and enterprise plans. Not checked yet
1 detail in Everything
Filter by Repository Labels in RepoSwitcher
Sep 25, 2025
· release notes
RepoSwitcher now supports filtering repositories by label to scope dashboard content.
Adds label selection in RepoSwitcher dropdown to filter repositories across the entire dashboard Not checked yet Auto-persists selected label in internal navigation links within RepoSwitcher Not checked yet Highlights matched text in RepoSwitcher search results Not checked yet
3 details in Everything
New: Bulk Label Assignment for Repositories
Sep 23, 2025
· release notes
Adds bulk label assignment for multiple repositories via the UI
Socket adds PyPI package version diff support alongside npm
Extends version diff functionality to PyPI packages with side-by-side insights for TAR, WHL, and EGG artifact types Not checked yet Adds accurate semantic version detection and comparison specifically for Python packages Not checked yet
2 details in Everything
Socket CLI v1.1.21 adds --compact-header for cleaner output and improves package manager interception.
Adds --compact-header flag to stream CLI output display Not checked yet Improves package manager interception for more accurate scanning Not checked yet Enhances detection of temporary package execution environments Not checked yet
3 details in Everything
Socket adds Export as CSV button on Organization Alerts page to download filtered alerts.
Socket CLI v1.1.20 adds terminal link support for richer output and improves Windows package manager compatibility.
Reintroduced Repository Page with Improved Label Management
Sep 19, 2025
· release notes
Reintroduced Repository details page with simplified label management and reorganized dependencies view.
Adds a reintroduced Repository details page providing quick access to dependencies, alerts, and scans. Not checked yet Introduces new, simplified label management for repositories. Not checked yet Moves attribution download to the top-right corner of the Dependencies page with support for organization-wide attribution. Not checked yet
3 details in Everything
Socket CLI v1.1.13–v1.1.15 expands the socket fix command with new CLI flags for export and dry-run modes.
Adds --output-file <path> flag to socket fix to save computed fixes to a JSON file Not checked yet Adds --only-compute flag to socket fix to compute fixes without applying them Not checked yet
2 details in Everything
Improved Alert Filtering with Semantic Grouping
Sep 17, 2025
· release notes
Improved Alert Filtering with Semantic Grouping organizes alert types into user-friendly categories via existing backend schemas.
Python SDK: Support for base_paths in FullScans and DiffScans
Sep 12, 2025
· release notes
Socket Python SDK adds base_paths parameter to FullScans and DiffScans APIs.
Python CLI: Enhanced Monorepo Support with Multiple Sub-paths
Sep 12, 2025
· release notes
Socket CLI --sub-path flag allows specifying multiple directories for a single monorepo workspace scan.
Adds --sub-path CLI argument to socket scan commands, allowing the flag to be passed multiple times to include several directories in a single workspace scan Not checked yet Integrates --sub-path with the base_paths parameter in the fullscans API endpoint Not checked yet
2 details in Everything
Python CLI: Monorepo Workspace Support
Sep 12, 2025
· release notes
Adds --sub-path and --workspace-name CLI flags to socket scan for individual monorepo workspaces
Adds --sub-path and --workspace-name options to the Python CLI enabling scanning of individual workspaces in monorepos while preserving git context. Not checked yet
1 detail in Everything
Socket moves Rust scanning from Experimental to Beta with full SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation
Enables full Rust project analysis including Cargo workspaces and Cargo.toml-only crates Not checked yet Unlocks full SBOM generation for Rust dependencies Not checked yet Activates Rust-aware supply chain checks in the general beta tier Not checked yet
3 details in Everything
Socket Fix 2.0 adds socket fix --id targeted remediation and Coana-powered upgrade planning across six ecosystems
socket fix --id <GHSA> allows targeted remediation of specific CVEs via a new CLI flag Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The --test flag is removed from the socket fix command; validation now relies on existing CI gates.
Python SDK: Align Endpoints and Tests with OpenAPI Spec
Sep 9, 2025
· release notes
Socket Python SDK adds apitokens.list() and base_path param
Adds apitokens.list() method to list API tokens programmatically. Not checked yet Adds base_path parameter support in file upload methods to override default URL paths. Not checked yet Updates multiple API endpoints to align with the OpenAPI OpenAPI A vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. specification, correcting URL paths and HTTP methods. Not checked yet
3 details in Everything
Tier 1 Reachability Now Available for Enterprise Teams
Sep 9, 2025
· release notes
Socket adds Tier 1 Reachability to scan for exploitable vulnerabilities in JS, TS, Python, Go, Java, and .NET
└──▷ USE IT
Run a scan focusing only on exploitable reachability in supported languages to filter out irrelevant CVEs.
shell
copy
socket scan create --reach
Adds socket scan create --reach flag for full application reachability analysis to identify actually exploitable vulnerabilities. Not checked yet Introduces Trace View capability showing exact call paths from source code into vulnerable functions for evidence-based remediation. Not checked yet Extends ecosystem support for Tier 1 Reachability analysis to JavaScript, TypeScript, Python, Go, Java, and .NET. Not checked yet
3 details in Everything
Add Autofix Command for CVEs in Alert Modal
Sep 4, 2025
· release notes
Socket CLI adds socket fix --ghsa <GHSA> command to compute and apply vulnerability fixes.
Adds the socket fix --ghsa <GHSA> subcommand to the Socket CLI for computing and applying fixes for vulnerabilities. Not checked yet
1 detail in Everything
API: Improved Error Handling for Malformed PURLs
Sep 4, 2025
· release notes
Socket API /v0/purl now returns 400 with actionable error details for malformed PURLs
GET /v0/purl returns a 400 Bad Request with specific guidance when a submitted PURL PURL A Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously. is malformed (e.g. missing pkg: prefix) or unknown. Not checked yet
1 detail in Everything
Python SDK: v3.0.3 Released with Complete API Coverage
Sep 2, 2025
· release notes
Socket.dev Python SDK v3.0.3 expands API coverage with new client modules for analytics, threats, and auditing.
Analytics , ThreatFeed, ApiTokens, AuditLog, and AlertTypes client classes now available in the Python SDK Not checked yet Enhanced DiffScans and Triage client functionality for scanning and workflow management Not checked yet New OpenAPIOpenAPI A vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. client support for API schema interaction Not checked yet
3 details in Everything
Alert Modal Updated to Show Affected Versions
Aug 29, 2025
· release notes
Socket's alert modal now shows specific affected versions for improved clarity.
Customize Pull Request Alert Comment Headers
Aug 29, 2025
· release notes
Socket lets you customize Pull Request alert comment headers via a Markdown editor in the dashboard.
Show Patched and Vulnerable Versions on Alerts Page
Aug 28, 2025
· release notes
Alerts page now displays vulnerable version range and first patched version for each alert.
Python CLI: Update to socketdev 3.0.0
Aug 23, 2025
· release notes
Socket Python CLI updates package name to socketdev and migrates dependency management to uv.
Migrates the package from socket to socketdev, making it the primary installable name for version 3.0.0. Not checked yet Moves dependency management tooling from Rye to uv, aligning with modern Python workflow standards. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! Users must replace socket package imports and dependencies with socketdev to use version 3.0.0.
Support SBOM Generation from Cargo.toml-only Crates
Aug 16, 2025
· release notes
Socket adds SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation for Cargo.toml-only crates missing lockfiles.
Adds support for generating Software Bill of Materials Software Bill of Materials A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. (SBOM) for Rust crates that contain only a Cargo.toml file without a Cargo.lock. Not checked yet
1 detail in Everything
Adds a PRs tab to the Scans page in Socket showing PR status for dependency changes and alerts
Adds PRs tab to the Scans page UI to view pull requests alongside their dependency change and alert status Not checked yet
1 detail in Everything
New Feedback Popover on Pull Request Scans Page
Aug 14, 2025
· release notes
Adds a feedback popover on the Pull Request Scans page to collect UX input via emojis and free-form text.
Socket adds resizable insights panels on Alerts, Dependencies, and Repositories pages
Document Support for Crates, NuGet, and RubyGems Ecosystems
Aug 7, 2025
· release notes
SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. export endpoints now officially document support for NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Crates, and RubyGems ecosystems
Add Insights Panel on Dashboard Repositories Page
Aug 6, 2025
· release notes
Adds an Insights panel with a time-series chart and label filters to the dashboard's Repositories page
Introduces the new Insights panel on the Dashboard Repositories page showing repository counts and time series trends Not checked yet Adds repository label filtering capability within the new Insights panel to update analytics views Not checked yet
2 details in Everything
Improve Support for Dependencies in Maven POM <profiles> Sections
Aug 5, 2025
· release notes
Socket now resolves dependencies defined in Maven POM <profiles> sections for conditional support.
Add Insights Panel on Dashboard Dependencies Page
Aug 5, 2025
· release notes
Socket adds an Insights Panel on the Dashboard Dependencies page with dependency counts and trend visualization
Adds a new Insights panel on the Dashboard Dependencies page providing direct and transitive dependency counts Not checked yet Adds a time series chart within the Insights panel for visualizing dependency trends Not checked yet
2 details in Everything
Fix Maven BOM Tarball Processing to Enable File Explorer Support
Aug 4, 2025
· release notes
Socket enables File Explorer visibility for Maven BOM BOM A Bill of Materials listing every component, library, and dependency in a software project; cyber tools use it to track what is in a codebase and flag known-vulnerable components quickly. projects
New: License Overlays for Custom License Management
Jul 31, 2025
· release notes
Socket adds License Overlays for custom license management, allowing per-package license identification and author info edits.
Adds the ability to create license overlays in Socket for customizing license information in dependency trees. Not checked yet Enables modifying license detection results on a per-package basis. Not checked yet Supports applying changes across versions using glob patterns (e.g., 1.*). Not checked yet Allows editing of license identifiers and author info for cleaner attribution files. Not checked yet Adds support for overlay notes to provide additional context. Not checked yet
+1 more
show less
Introduces the Settings → Legal → License Overlays interface for viewing and managing overlays. Not checked yet
6 details in Everything
Add RepoSwitcher to Dashboard for Improved Navigation
Jul 31, 2025
· release notes
Adds RepoSwitcher component to Socket Dashboard for global repository filtering
Adds RepoSwitcher drop-down to the Dashboard next to the OrgSwitcher, acting as a global repository filter for PR Stories, Repositories, Dependencies, Alerts, Scans, PRs, and Analytics pages. Not checked yet Adds dependencies and scans columns to the Repositories page in the dashboard UI. Not checked yet Applies the global repository filter to the Alerts and Scans tables and removes unnecessary columns for a cleaner view. Not checked yet
3 details in Everything
Socket adds Rust/Cargo ecosystem support with crate search, security scores, and experimental SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation.
Adds socket.dev crate search for all users covering the Rust and Cargo ecosystem Not checked yet Provides security scores, maintainer info, and dependency insights for Rust packages Not checked yet Enables experimental SBOM generation for enterprise Rust projects with full workspace support Not checked yet
3 details in Everything
Support for GitHub Merge Queues Now Available
Jul 31, 2025
· release notes
Socket GitHub app triggers full scans and check runs for commits landing via GitHub Merge Queues
Requires the Merge queue permission for the Socket GitHub app; existing orgs will see a permission request to upgrade Not checked yet
1 detail in Everything
Precomputed Reachability Analysis Is Now Available
Jul 30, 2025
· release notes
Precomputed reachability analysis now flags unreachable CVEs with no setup.
Adds automatic precomputed reachability analysis that flags up to 80% of vulnerabilities as irrelevant using only manifest files like package-lock.json and requirements.txt Not checked yet Introduces a new CVE Reachability section in alert modals and a filter by reachability to prioritize actionable findings Not checked yet Sets unreachable CVEs to default to the monitor action instead of active remediation Not checked yet
3 details in Everything
New Vulnerability Reachability Funnel Chart
Jul 30, 2025
· release notes
Socket adds a CVE Funnel Chart on the Overview page to visualize vulnerability reachability across four stages.
Experimental Protection for Chrome Extensions
Jul 29, 2025
· release notes
Experimental pilot for scanning Chrome extensions for malware and supply chain risks
Expands Socket's scope to scan Chrome extensions for malware, risky permissions, and silent supply chain attacks Not checked yet
1 detail in Everything
Socket MCP Now Available in Claude Desktop Extensions
Jul 29, 2025
· release notes
Socket MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. now available as a Claude Desktop Extension enabling in-chat dependency scanning
Socket adds beta support for scanning Scala and Kotlin JVM JVM The Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. dependencies.
Socket adds UI popover to view the last 7 EPSS EPSS Exploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. scores with higher precision
Adds a new UI popover that displays the last 7 EPSS scores for dependencies Not checked yet Increases precision for fractional digits in the EPSS score history renderings Not checked yet
2 details in Everything
Dependency Search API now accepts purl list in request body
New Alerts Trend Chart in Insights Panel
Jul 24, 2025
· release notes
Insights panel on Alerts page gains a trend chart to visualize alert patterns over time.
Increased File Limit for Full and Diff Scans
Jul 24, 2025
· release notes
Socket increases the maximum number of files for full-scan and diff-scan API submissions from 1,000 to 5,000.
Raises the maximum file limit for full-scan and diff-scan API submissions from 1,000 to 5,000 files Not checked yet Enables larger projects and repos to be scanned without hitting file count limits Not checked yet
2 details in Everything
EPSS Score Now Visible in Alert Modal
Jul 19, 2025
· release notes
EPSS EPSS Exploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. score and percentile now visible in the AlertModal for vulnerability prioritization.
Adds EPSS score and percentile display to the AlertModal UI component Not checked yet
1 detail in Everything
Alert Modal Now Displays Known Exploited Vulnerabilities (KEV) Data
Jul 8, 2025
· release notes
Socket Dashboard alert modal now displays CISA Known Exploited Vulnerabilities CISA Known Exploited Vulnerabilities A catalog maintained by the US Cybersecurity and Infrastructure Security Agency listing CVEs confirmed to have been actively exploited in the wild, which cyber tools use as a high-signal prioritization feed for patching and scanning. (KEV KEV CISA's Known Exploited Vulnerabilities catalog, a list of vulnerabilities with evidence of exploitation in real attacks. It helps teams prioritize fixes for problems attackers already use. ) data.
Python CLI: GitLab api Event Support + Safer License File Naming
Jul 4, 2025
· release notes
Socket Python CLI adds --license-file-name flag and GitLab API event support
Adds --license-file-name CLI flag to specify a static output filename for license reports instead of auto-generated names based on repo/branch Not checked yet
1 detail in Everything
Socket adds comprehensive SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation for Rust/Cargo projects via Cargo.toml and Cargo.lock files
Redesigned Scan Pages in the Dashboard
Jul 3, 2025
· release notes
Socket updates Dashboard Scan Pages with simplified headers and a redesigned Insights panel for easier access.
Redesigned SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. Report Page UI with simplified headers showing only repository, PR, and timestamp. Not checked yet Removed redundant information such as duplicate Manifests labels and UUID UUID A universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide. -heavy scan IDs from scan pages. Not checked yet Updated Insights panel layout and control buttons to improve accessibility within the Dashboard. Not checked yet
3 details in Everything
View Diff Scans by ID in the Dashboard
Jun 26, 2025
· release notes
Socket Dashboard now supports viewing Diff Scans directly by ID via a new dedicated page and API routes.
Adds a dedicated page on the Socket Dashboard to view diff scans using their unique Diff Scan ID Not checked yet Updates internal URLs in the API and GitHub app to link to the new diff scan route Not checked yet Enables tracking and sharing of diff scans as standalone resources powered by stored multi-SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. data Not checked yet
3 details in Everything
Changelog Notification Now Functions as Read Indicator
Jun 26, 2025
· release notes
Changelog notification dot now clears immediately on open rather than persisting for 48 hours
Improves the pink dot indicator on the Socket dashboard to disappear immediately when the Help & Info popover is opened Not checked yet
1 detail in Everything
Socket adds /alert-types API endpoint to fetch detailed alert metadata programmatically.
Adds the /alert-types API endpoint for retrieving detailed information about specific alerts Not checked yet Enables fetching alert context outside the UI to streamline integrations Not checked yet
2 details in Everything
New Collapse Sidebar Button in the Dashboard
Jun 23, 2025
· release notes
Socket adds a collapse/expand button to the dashboard sidebar
Socket MCP Now Available as a Hosted Service
Jun 19, 2025
· release notes
Socket MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. is now available as a hosted service on https://mcp.socket.dev for direct client integration.
Adds the option to use the Socket MCP server via the hosted service at https://mcp.socket.dev instead of running it locally. Not checked yet
1 detail in Everything
New Copy-to-Clipboard Button in File Viewer
Jun 19, 2025
· release notes
Socket adds a copy-to-clipboard button to the File Explorer header for quick snippet sharing.
Adds a copy-to-clipboard button in the File Viewer header to quickly grab and share code snippets. Not checked yet
1 detail in Everything
Socket CLI v1 introduces streamlined commands with automated defaults for org/cwd and new subcommands like socket scan diff.
Dropped the need to manually pass org and cwd by using stored defaults and interactive prompts when needed Not checked yet Reworked socket analytics, socket audit-log, and socket repository commands for simpler, more consistent usage Not checked yet Added new socket scan diff, socket package score, and socket scan report commands to replace deprecated ones Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! Manual passing of org and cwd arguments is no longer supported; users must use stored defaults or prompts! Older commands are deprecated and replaced by new subcommands (socket scan diff, socket package score, socket scan report)! The CLI now defaults to the v1 experience, requiring migration via the provided guide
Socket adds blog search and back-button navigation on its website.
Adds a search bar to the Socket site for finding blog posts. Not checked yet Adds a Back button on individual blog post pages. Not checked yet
2 details in Everything
Socket adds a manual refresh button on the Alerts page to get fresher data outside the standard cycle
Adds a Request refresh action in the Alerts page top-right '...' menu for Enterprise (every 6 hours) and Team (every 12 hours) users. Not checked yet Displays the timestamp of the last manual refresh on the Alerts page. Not checked yet Shows an error message when the rate limit for manual alert refresh is exceeded. Not checked yet
3 details in Everything
New UI filter to distinguish manual vs automated alert resolutions in Socket.
Adds the Alert Action Source filter to the alert table via UI path Filter → Alert Action Source Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The policy coverage filter is removed; users can no longer filter by policy coverage in the alert table.
Support for pylock.toml (PEP 751) Now Available
Jun 4, 2025
· release notes
Socket adds support for analyzing pylock.toml (PEP 751 PEP 751 A draft Python packaging standard that defines a lock file format for recording exact dependency versions, giving cyber tools a reproducible, machine-readable way to pin their dependency trees. ) Python lock files
Supports pylock.toml (PEP 751) Python lock file format for secure, reproducible builds and hash-based security analysis Not checked yet
1 detail in Everything
New: Rename Repository Labels via API
Jun 4, 2025
· release notes
Socket adds PUT /labels endpoint to rename repository labels via API
Python SDK: Added Support for Historical and Label Endpoints
Jun 2, 2025
· release notes
Socket Python SDK adds endpoints for label management and historical alert data access
Adds labels endpoint group supporting create, list, get, and delete operations to manage labels programmatically Not checked yet Adds labels/settings endpoints allowing get, update, and delete configuration for specific labels Not checked yet Adds association capabilities to link or unlink labels with alerts via the SDK Not checked yet Adds historical endpoint group for listing past alerts and viewing trend data over time Not checked yet Adds snapshot management via list and create operations within the historical data endpoint Not checked yet
5 details in Everything
New Alerts Page is Generally Available
May 30, 2025
· release notes
Socket GA release: new faster Alerts page with PDF export, filtering, and note-taking capabilities.
Makes the redesigned Alerts page the default view for all users Not checked yet Adds PDF export option for alert lists via the new UI Not checked yet Enables grouping alerts by repository in the Alerts view Not checked yet Adds filtering by priority level within the Alerts interface Not checked yet Supports search queries by package name, CVE ID, and license name Not checked yet
+3 more
show less
Allows adding notes to individual alerts in the detail view Not checked yet Permits changing the alert action directly from the UI Not checked yet Displays the reason for a given alert action (e.g., security policy or repository label) Not checked yet
8 details in Everything
Socket MCP: Real-Time Dependency Scoring for AI Tools
May 28, 2025
· release notes
New Socket MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server adds real-time dependency scoring via Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. for AI tools like Copilot and Claude.
Launches socket-mcp, an experimental MCP server that brings real-time dependency scoring to AI-assisted development Not checked yet Enables tools such as GitHub Copilot, Claude, and other LLM LLM A large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. integrations to query Socket’s depscore API directly during code generation Not checked yet
2 details in Everything
Socket now creates a GitHub check run on every commit regardless of manifest files for consistent visibility.
Adds GitHub check run creation for all commits processed by the Socket GitHub App, even without manifest files. Not checked yet
1 detail in Everything
Socket adds a new threat feed API endpoint for syncing new and updated threats.
Socket rebuilds Organization Alerts Beta page with server-side filtering and All tab for faster large-org views
Adds All tab to Organization Alerts Beta UI to view all alerts in one place Not checked yet Improves performance via server-side filtering and search powered by analytics backend Not checked yet
2 details in Everything
New: Socket Fix for Safe, Automated Dependency Upgrades
Apr 25, 2025
· release notes
Socket introduces socket fix CLI for automated, safe dependency upgrades with --test and --autopilot modes
└──▷ TRY IT
Validate dependency upgrades safely by running the test suite before applying changes.
Adds the socket fix subcommand to automatically update vulnerable dependencies Not checked yet Adds --test mode to run tests during upgrade validation Not checked yet Adds --autopilot mode for automated testing and merging in CI Not checked yet
3 details in Everything
Historical Analytics (Beta) Now Available
Apr 24, 2025
· release notes
Socket adds 30 days of historical scan data access and new API endpoints for exporting past alerts.
New: Repository Labels + Security Policies
Apr 22, 2025
· release notes
Socket adds repository labels and label-specific security policies via API
Adds custom labels to repositories for organizing repos by stack or sensitivity Not checked yet Enables filter, sort, and search functionality based on repository labels Not checked yet Allows applying custom security policies to specific labels instead of only org-wide settings Not checked yet Permits overriding the org-wide security policy for labeled sets of repositories Not checked yet Supports automation of label management and policy application via the public API Not checked yet
5 details in Everything
CDX Export Now Supports All Ecosystems
Apr 22, 2025
· release notes
Socket CDX export endpoint now supports all ecosystems instead of a hardcoded subset.
Socket now scans .NET projects (NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. /MSBuild MSBuild Microsoft's build engine for .NET and C++ projects, shipping with Visual Studio and the .NET SDK; cyber tools use it because it can execute arbitrary tasks and inline C# code, making it a living-off-the-land execution vector. ) for supply chain threats in public beta.
Adds support for scanning .NET ecosystems using NuGet and MSBuild for supply chain threats Not checked yet Enables deep analysis of .NET dependency graphs including transitive and conditionally imported packages Not checked yet Improves SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. accuracy for .NET projects Not checked yet
3 details in Everything
Exclude Ecosystems from Socket CLI Scans
Apr 21, 2025
· release notes
Socket CLI now supports excluding specific ecosystems from scans via Supported Files API.
Set Repo Visibility When Creating via Python CLI
Apr 21, 2025
· release notes
Socket's Python CLI now supports specifying public or private visibility when creating repositories
The socket Python CLI now lets you choose whether a newly created repository should be public or private. Not checked yet
1 detail in Everything
Socket now generally supports Go language scanning for supply chain threats with configurable alerts.
Adds Go ecosystem support to socket scanning, detecting obfuscation, backdoors, and exec.Command misuse in projects with go.mod and go.sum files Not checked yet Enables management of Go-specific alerts via project settings Not checked yet
2 details in Everything
Slack Integration Now Available in Python CLI
Apr 16, 2025
· release notes
Socket CLI gains Slack plugin for notifications.
Jira Integration Now Available in Python CLI
Apr 15, 2025
· release notes
Socket CLI adds Jira integration for auto-creating tickets on Blocked/Warning issues
Rubygems Ecosystem Support Now Generally Available
Apr 15, 2025
· release notes
Socket generally adds Rubygems ecosystem support and enables Ruby scanning by default
Adds general availability for Ruby project supply chain threat detection via Gemfile.lock analysis Not checked yet Enables Ruby scanning by default for all users Not checked yet
2 details in Everything
Reintroduced Dependency Reachability Toggle with Improved Behavior
Apr 15, 2025
· release notes
Socket reintroduces the Dependency Reachability toggle in organization settings with improved state persistence.
Adds a dependency reachability toggle to organization settings for all paid plans, allowing users to enable or disable unused dependency identification via code analysis. Not checked yet
1 detail in Everything
Improved Alert Details with Remediation Suggestions and Better CVE Readability
Apr 15, 2025
· release notes
Socket dashboard AlertModal now shows remediation suggestions and renders CVE descriptions in Markdown.
Adds Remediation Suggestions to the AlertModal UI component for actionable guidance. Not checked yet Renders CVE descriptions with Markdown formatting in the dashboard for improved readability. Not checked yet
2 details in Everything
New Toggle to Enable Reachability Analysis in Organization Settings
Apr 10, 2025
· release notes
Adds a toggle to enable dependency reachability analysis in organization settings
Re-added Support for URL Search Params on the Repositories Page
Apr 4, 2025
· release notes
Re-added URL search params (page, query, sort_by) on the Repositories page for shareable filtered views
page, query, and sort_by URL parameters are supported again on the Repositories dashboard page. Not checked yet
1 detail in Everything
New Tabs for Alerts, Dependencies, and Scans on Repository Pages
Apr 2, 2025
· release notes
Adds Alerts, Dependencies, and Scans tabs to Socket dashboard repository pages
Adds an Alerts tab (default) showing a detailed table of current repo alerts Not checked yet Adds a Dependencies tab that pre-filters org dependencies to the selected repository Not checked yet Adds a Scans tab for accessing scan results on repository pages Not checked yet
3 details in Everything
Improved Scan Performance for Socket Python CLI
Apr 1, 2025
· release notes
Socket Python CLI now excludes __pycache__ and node_modules folders by default to improve scan performance.
Significantly speeds up Python scans by preventing duplicate results Not checked yet
1 detail in Everything
Redesigned Repositories Page with Alert Severity Breakdown
Apr 1, 2025
· release notes
Socket adds severity breakdown and column sorting to the Repositories page dashboard.
Redesigned the Repositories page in the dashboard to include alert count summary broken down by severity for each repository Not checked yet Added support for column sorting on the new Repositories table view Not checked yet
2 details in Everything
Filter for Fixable Alerts in Bulk Packages API
Mar 11, 2025
· release notes
Adds fixable query param and alert.fix property to the Socket.dev bulk packages API
Adds fixable=true query option to the batch PURL PURL A Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously. endpoint to retrieve only fixable artifact alerts. Not checked yet Adds alert.fix object with type (cve | upgrade ) and description fields to alert responses. Not checked yet
2 details in Everything
Bulk Packages API Now Respects Org Security and License Policies
Mar 6, 2025
· release notes
Bulk Packages API now applies org security and license policies
Adds organization policy enforcement to the Bulk Packages API (purl) endpoint Not checked yet
1 detail in Everything
Fixed diff_report_url in Full Scan Diff Endpoint
Mar 3, 2025
· release notes
Full Scan Diff API now uses Full Scan IDs for diff_report_url
diff_report_url field in the Full Scan Diff Endpoint now returns URLs generated using Full Scan IDs instead of SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. IDs. Not checked yet Response body of the Full Scan Diff Endpoint now includes repo and org slugs. Not checked yet
2 details in Everything
Socket adds query parameters branch, pull_request, commit_hash to Full Scan List API
Improved Bearer Authentication Header Support on All API Routes
Feb 28, 2025
· release notes
Socket API now accepts standard unencoded Bearer tokens Bearer tokens A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. on all routes
Removes mandatory base64 encoding for Authorization: Bearer <token> headers across all API routes Not checked yet
1 detail in Everything
New 'compact' Parameter for Batch PURL and Full-Scans API Endpoints
Feb 19, 2025
· release notes
Socket adds compact parameter to Batch PURL PURL A Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously. and Full-Scans API endpoints
Enables high-efficiency integrations by stripping optional data from API responses to reduce payload size Not checked yet
1 detail in Everything
New Integration: Microsoft Sentinel Support Added to Socket SIEM Connector
Feb 18, 2025
· release notes
Socket SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. Connector adds direct Microsoft Sentinel support for unified alerting
Dashboard Now Displays Full Numbers for Better Readability
Feb 14, 2025
· release notes
Dashboard now displays full numbers with thin spaces for clarity
Adds thin-space separation and clearer formatting (e.g., 1.2B) to dashboard metrics for better readability Not checked yet
1 detail in Everything
New Discovery Period Filter for Threat-Feed API
Feb 14, 2025
· release notes
Socket Threat-Feed API adds discovery_period filter for date-based threat querying
Adds discovery_period parameter to Threat-Feed API endpoints to filter threats by discovery date Not checked yet
1 detail in Everything
Fine-Tuned Full Scan Control with New Query Parameter for License Details
Feb 14, 2025
· release notes
Socket adds include_license_details query param to streaming full_scan API for scan performance control.
└──▷ USE IT
Skip license details in a full scan to improve performance when scanning large organizations.
code
copy
import socketdev from '@api/socketdev';
socketdev.getOrgFullScan({
include_license_details: 'false',
org_slug: 'org_slug',
full_scan_id: 'full_scan_id',
accept: 'application/x-ndjson'
})
.then(({ data }) => console.log(data))
.catch(err => console.error(err));
Alert Table Search Now Supports CVE and License IDs
Feb 13, 2025
· release notes
Dashboard Alert Table Search now supports filtering by CVE and License IDs
Adds CVE ID recognition to the dashboard alerts page search field Not checked yet
1 detail in Everything
socket.yml Now Supports disableCommentsAndCheckRuns Override
Feb 11, 2025
· release notes
socket.yml now supports disableCommentsAndCheckRuns override for repository-specific GitHub App configuration.
Adds disableCommentsAndCheckRuns as an overridable setting in socket.yml to control GitHub App behavior at the repository level. Not checked yet
1 detail in Everything
Search and Group By Now Reflected in Alert Table URL
Feb 10, 2025
· release notes
Alert table search and Group By selection are now reflected in the URL for persistence and sharing.
Alert Table Filters Are Now Shareable via URL
Feb 6, 2025
· release notes
Alert Table filters are now persisted in the browser URL for shareable views
Browser URL now dynamically reflects Alert Table filter selections to enable sharing and persistence Not checked yet
1 detail in Everything
New: API Scopes for Historical Alerts Access
Feb 5, 2025
· release notes
Adds alerts:list and alerts:trend API scopes to Socket for accessing historical alert endpoints
Adds the alerts:list scope required to fetch a list of historical alerts via GET /v0/orgs/:org_slug/alerts/historical Not checked yet Adds the alerts:trend scope required to fetch historical alert trend data via GET /v0/orgs/:org_slug/alerts/historical/trend Not checked yet
2 details in Everything
New: Public API Endpoints for Historical Alerts and Trends
Feb 4, 2025
· release notes
New API endpoints provide programmatic access to historical alert data and trends.
Adds /v0/orgs/:org_slug/alerts/historical endpoint Not checked yet Adds /v0/orgs/:org_slug/alerts/historical/trend endpoint Not checked yet
2 details in Everything
Expanded Alert Metadata in Full-Scan Diffs
Jan 30, 2025
· release notes
Full-scan diff endpoint now includes expanded metadata for alerts and artifacts
New Modal Design for Alert, Dependency, and Threat Tables
Jan 16, 2025
· release notes
Alert, Dependency, and Threat tables now use modals instead of sidebars for detailed inspection
Inspection of items in the Alert Table, Dependency Table, and Threat Feed Table opens a modal interface instead of a sidebar. Not checked yet Alert modals now organize details into explicit sections: Alert details, Artifact details, and Installation details, with reorganized content hierarchy. Not checked yet Triage notes within these tables gain an autosave feature and a sticky note visual style. Not checked yet
3 details in Everything
Added: Links to Specific File Locations for Alerts and License Info
Jan 14, 2025
· release notes
Socket adds #T URL fragments to alerts and license info links for direct file navigation
Alerts and license information now include links to specific locations within the relevant file using the #T URL fragment. Not checked yet
1 detail in Everything
New: Dependency Tree in the Dependencies Tab Sidebar
Jan 14, 2025
· release notes
Socket adds a Dependency Tree view accessible directly from the sidebar in the Dependencies tab.
Introducing created_at Sort Order in the Threat-Feed API
Jan 3, 2025
· release notes
Socket adds created_at sort order to the Threat-Feed API
New Query Parameter: is_human_reviewed for Threat-Feed API
Dec 17, 2024
· release notes
Socket adds is_human_reviewed query parameter to Threat-Feed API
Socket adds parsing support for uv.lock uv.lock A machine-generated lockfile produced by uv, Astral's Python package manager, that pins every dependency to an exact version and hash so builds are perfectly reproducible across machines. dependency files.
Adds uv.lock file parsing to expand dependency tracking for Python projects. Not checked yet
1 detail in Everything
Introducing a New "AI-Detected Possible Typosquat" Alert
Dec 6, 2024
· release notes
Socket introduces AI-detected possible typosquat alerts
Adds AI-detected possible typosquat alert to distinguish AI-flagged typosquat threats from human-reviewed ones Not checked yet
1 detail in Everything
New Support for pipfile.lock Files in Python Projects
Dec 6, 2024
· release notes
Socket adds ParsePipfileLock task to parse pipfile.lock files for Pipenv projects
Enhanced PDF Export for Organization Alerts
Dec 5, 2024
· release notes
Enhanced PDF export for organization alerts now includes repository and branch details
Organization alert PDF exports now include repositories and branches fields for each alert Not checked yet
1 detail in Everything
Package search now accepts PURLs and ecosystem prefixes for direct navigation.
Adds support for full and abbreviated Package URLs (e.g., pkg:npm/react@18.0.0 or npm/react@18.0.0) in the package search bar to jump directly to a package Not checked yet Enables ecosystem switching by typing prefixes like pypi/ or rubygems/ followed by space and query text, with case-insensitive matching Not checked yet
2 details in Everything
npm Security Holding Packages Now Flagged as Known Malware
Nov 21, 2024
· release notes
Socket adds Known Malware alerts for npm security holding packages to clarify threat status of removed placeholders.
New Filters Added to the Threat Feed Endpoint
Nov 21, 2024
· release notes
Threat feed endpoint now supports name, version, and ecosystem query parameters for precise filtering.
Focus on What Matters: New Security Policy Filter for Alerts
Nov 21, 2024
· release notes
Socket adds Per Security Policy alert filter and updates SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. dependency visualization
Adds the new Per Security Policy filter to alert management, flagging alerts as accepted or ignored based on your security policy configuration. Not checked yet Updates SBOM dependency visualization so that dependencies with zero alerts or all ignored alerts are rendered as neutral white rectangles. Not checked yet
2 details in Everything
Weekly Download Counts Now Available on Package Search Results
Nov 20, 2024
· release notes
Socket.dev now displays weekly download counts alongside package search results for npm.
Socket Dashboard Reports page now supports searching by repo/branch/commit and filtering by creation date.
Adds search capability to filter Dashboard Reports by repository name, branch name, or commit message Not checked yet Adds filtering of Dashboard Reports by creation date (e.g., the past X days) Not checked yet Improves table UI with cleaner visuals and more on-brand design Not checked yet
3 details in Everything
New GET /rest/findings/export and UI export allow programmatic and manual access to organization license policies via Socket's License Policy API
Adds the GET https://api.socket.dev/v0/orgs/{org_slug}/settings/license-policy endpoint to view an organization's license policy settings programmatically. Not checked yet Adds the PATCH https://api.socket.dev/v0/orgs/{org_slug}/settings/license-policy endpoint to edit an organization's license policy settings programmatically. Not checked yet
2 details in Everything
Improved Capability Alerts: File Locations Now Included
Nov 8, 2024
· release notes
Socket Capability alerts now include specific file locations for risks.
Capability alerts now display the specific files associated with potential risks. Not checked yet
1 detail in Everything
Socket Web Extension gains Go language support with pkg.go.dev integration and real-time threat detection
Adds full Go package threat detection and security metrics in the Socket Web Extension for Chrome and Firefox Not checked yet Enables direct linking to https://pkg.go.dev and external module URLs from detected Go packages Not checked yet Supports parsing of Go PURLs (e.g., pkg:golang/google.golang.org/genproto) within browser context Not checked yet
3 details in Everything
Socket Optimize Update: Introducing --pin & --prod Options, Enhanced Workspaces, and Node 18+ Support
Oct 31, 2024
· release notes
Enhanced workspace support and Node.js 18+ compatibility in Socket Optimize.
Improved workspace support for multi-package handling Not checked yet Upgraded packages to support Node.js 18+ Not checked yet Added more intuitive error messages Not checked yet
3 details in Everything
Native Code Alert Enhanced to Support Multiple Ecosystems
Oct 16, 2024
· release notes
Native Code Alert now scans multiple ecosystems beyond npm, including prebuilt binaries.
Expands the Native Code alert to detect prebuilt binaries and ecosystem-specific files across various programming languages, rather than just binding.gyp files in npm packages. Not checked yet
1 detail in Everything
New: Support for the Yarn 'resolutions' Field
Oct 5, 2024
· release notes
Socket now supports the Yarn resolutions field for dependency override analysis.
Adds support for parsing and analyzing the resolutions field in Yarn lockfiles to detect enforced dependency versions. Not checked yet
1 detail in Everything
Full Scans API Expanded: More Dashboard Metrics and Better Repository Controls
Oct 5, 2024
· release notes
Full Scans API expands metadata fields and dashboard metrics; drops branch name requirement.
API: Full scans now support api, github, gitlab, bitbucket and azure metadata fields in the dashboard Not checked yet API: Creating a full scan via the API no longer requires a branch parameter Not checked yet UI: Repositories created by the GitHub app can now be deleted from the Organization Dashboard Not checked yet
3 details in Everything
Web Extension Revamped: Improved Performance, UI Enhancements, and Essential Bug Fixes
Oct 3, 2024
· release notes
Socket Web Extension adds stats reset button and improves SPA link handling
Adds a reset button in the extension popup to reset accumulated statistics. Not checked yet
1 detail in Everything
Introducing Support for Jenkins Jobs
Sep 25, 2024
· release notes
Socket adds Jenkins Job integration for CI/CD security automation
Adds support for Jenkins Jobs to Socket's CI/CD integrations Not checked yet
1 detail in Everything
Initial Version 1.0.9 of the Socket Python SDK has been released!
Sep 13, 2024
· release notes
Socket Python SDK 1.0.9 adds report filtering, API timeouts, and SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. dict generation
Adds from_time parameter to report.list() function for unix timestamp filtering Not checked yet Adds timeout argument to socketdev class constructor for API call duration control Not checked yet Adds sbom.create_packages_dict() function for generating package dictionaries Not checked yet
3 details in Everything
Socket CLI adds socket threat-feed command to fetch threat feed data via flags.
Adds the socket threat-feed subcommand to retrieve Socket's threat feed directly from the CLI. Not checked yet Adds --perPage, --page, --direction, and --filter flags to socket threat-feed for pagination and filtering. Not checked yet Adds --json flag to socket threat-feed to return output as a JSON object. Not checked yet
3 details in Everything
GitHub App Now Creates Full-Scans on Push Events
Sep 6, 2024
· release notes
GitHub app now creates full-scan resources on push events, accessible via the full_scans API endpoint
Adds the full_scans API endpoint to retrieve a paginated list of full scans for an organization, excluding SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. artifacts Not checked yet
1 detail in Everything
Socket adds experimental Ruby gem security scanning and core alerts
Socket introduces new dashboard analytics with graphs for alerts and CSV/JSON export
Adds dashboard analytics view showing total critical/high alerts in main branches, daily merged alerts, prevented merges, and top 5 alert types Not checked yet Adds data filters to display ingested data from the last 7, 30 or 90 days Not checked yet Enables exporting dashboard data as CSV or JSON Not checked yet
3 details in Everything
API: Added Support for a "from" Query Filter to the Audit-Log Endpoint
Aug 28, 2024
· release notes
API: Added Support for a from Query Filter to the Audit-Log Endpoint
New Alert: Suspicious Stars on GitHub
Aug 27, 2024
· release notes
Socket adds Suspicious Stars on GitHub high-severity supply chain alert
Version 1.0.17 of the Socket Python CLI has been released!
Aug 22, 2024
· release notes
Socket Python CLI v1.0.17 adds GitLab web event support and handles unknown events gracefully.
Socket introduces Low Noise, Default, and Higher Noise default security policies with new alert types (Block, Warn, Monitor, Ignore).
Adds three customizable default security policy profiles: Low Noise (traditional SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. ), Default, and Higher Noise to reduce alert noise and manage false positives. Not checked yet Enables four new alert types: Block, Warn, Monitor, and Ignore for granular control over CI/CD flow and dashboard visibility. Not checked yet Allows users to lock in specific settings during the transition period (August 14-28, 2024) before new defaults automatically take effect on August 28. Not checked yet
3 details in Everything
Socket web extension adds PyPI/Go/Maven support and threat detection metrics
Expands threat detection to PyPI, Go, and Maven ecosystems beyond previous scope Not checked yet Displays real-time threat detection metrics directly within the browser extension UI Not checked yet Reduces extension footprint by 1500x (~0.02MB) with lower memory usage Not checked yet
3 details in Everything
PDF Export for Dependencies in the Dashboard
Aug 13, 2024
· release notes
PDF export capability added to Socket Dashboard for dependency views, alert tables, and overview statistics.
Adds PDF export capability for the Dependency Overview view in the dashboard Not checked yet Adds PDF export capability for the Alert Table view (up to 2,500 alerts) in the dashboard Not checked yet Adds PDF export capability for organization overview statistics, repositories, and threat feed samples in the dashboard Not checked yet
3 details in Everything
Version 1.0.1 of the Socket Python CLI has been released!
Jul 30, 2024
· release notes
Adds pull_request event support with opened state handling to Socket Python CLI
Version 1.0.0 of the Socket Python CLI has been released!
Jul 29, 2024
· release notes
Socket Python CLI v1.0.0 adds Security Policy Modes (Block/Warn) and --ignore-commit-files flag.
--ignore-commit-files option added to scan all manifest files regardless of commit history Not checked yet Security Policy Modes Block and Warn now supported for CI integration Not checked yet Console output includes CI Status indicating Block/Warn policy result Not checked yet
3 details in Everything
New 'from' and 'repo' fields added to reports endpoint
Jul 20, 2024
· release notes
Socket adds from and repo query parameters to its reporting API endpoints for filtered scanning.
Adds from (unix timestamp) and repo (repo slug) querystring filters to the GET /report/list endpoint Not checked yet Adds from (unix timestamp) and repo (repo slug) querystring filters to the GET /orgs/{org_slug}/full-scans endpoint Not checked yet
2 details in Everything
Use yarn alternative resolution by default
Jul 18, 2024
· release notes
Socket now uses a new yarn module resolution algorithm by default to generate npm v1 lockfiles from yarn.lock.
Replaces the previous yarn resolution method with an alternative algorithm that maps package.json dependencies to the yarn lock file and traverses it to generate an npm v1 lockfile for module resolution. Not checked yet
1 detail in Everything
Socket API adds new 'licenseattrib' option to the /v0/purl endpoint
Jul 18, 2024
· release notes
Socket API adds licenseattrib query parameter to /v0/purl for license attribution data
Add unmaintained alert for Maven packages
Jul 16, 2024
· release notes
Socket expands its Maven package analysis capabilities.
Maven packages are now evaluated for maintenance status. Not checked yet
1 detail in Everything
Display alert count on alert package pages
Jul 16, 2024
· release notes
Adds estimated alert count badges to alerts/[alertType]/packages pages to gauge alert frequency.
Add Deprecated alert for PyPI packages
Jul 16, 2024
· release notes
Socket adds Deprecated alert for PyPI packages to detect yanked releases
Adds support for detecting Deprecated alerts on PyPI packages marked as yanked in their release metadata Not checked yet
1 detail in Everything
Adds a new API endpoint to export CycloneDX CycloneDX An open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. SBOMs SBOMs A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. from SocketSBOM reports or full scan IDs.
GET /v0/orgs/{org_slug}/export/cdx/{id} — Export CycloneDX SBOM SBOM A software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. from a report ID or full scan ID Not checked yet
1 detail in Everything
Socket CLI: Add dependencies search command
Jun 27, 2024
· release notes
A new CLI capability allows practitioners to programmatically search for dependencies across their organization using the Socket cyber tooling.
Add socket dependencies search command to query organization-wide dependency usage. Not checked yet
1 detail in Everything
Socket CLI adds socket audit-log command to retrieve organizational audit trails.
Socket CLI gains the repos subcommand with CRUD CRUD The four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information. operations for managing organizational repositories.
Adds the socket repos subcommand to view, list, create, update, and delete organization repositories Not checked yet
1 detail in Everything
Socket CLI adds socket scan command with create, list, stream, delete and metadata subcommands for full scans.
socket scan command is added to control full scans directly from the CLI Not checked yet socket scan list <org slug> lists available full scans for an organization Not checked yet socket scan create <org slug> <flags> creates a new full scan Not checked yet socket scan stream <org slug> <full scan ID> [output path] streams or exports scan results Not checked yet socket scan delete <org slug> <full scan ID> removes a specified full scan Not checked yet
+1 more
show less
socket scan metadata <org slug> <full scan ID> retrieves metadata for a specific full scan Not checked yet
6 details in Everything
Filter alerts by alert triage in GitHub bot
Jun 13, 2024
· release notes
Adds filtering of Socket GitHub bot alerts by their triage status.
Socket for GitHub now allows users to filter alerts by alert triage Not checked yet
1 detail in Everything
Socket implements an audit log API endpoint to match dashboard features.
Adds the GET /api/v1/audit-logs endpoint for retrieving audit logs. Not checked yet
1 detail in Everything
Add API endpoints for license data and attribution
Jun 3, 2024
· release notes
Adds /license-details and /license-attrib API endpoints to retrieve license and attribution data for artifacts via purl.
Adds /license-details endpoint to get artifact license information Not checked yet Adds /license-attrib endpoint to get artifact license attribution information Not checked yet
2 details in Everything