The daily firehose — everything the toolchain shipped today, already filtered.
We read every release from the 1309 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.
READ AS
Focus:What features shipped and what problems they solve, plus launches, packaging and where the market is moving.
Leaves out:Command-line flags, API-only deltas, usage examples, and releases that are only refinements.
Focus:New security controls, new APIs, and product improvements you can put to work, plus anything an upgrade breaks.
Leaves out:Launch and marketing news, governance, pricing, and documentation changes with no operational effect.
Focus:Dashboards, reporting, and anything you can quantify: metrics, coverage, risk scores, compliance impact, vendor moves.
Leaves out:Settings, flags, API and command-line detail, library bumps, and minor releases with no reporting or posture angle.
Focus:API, SDK and MCP changes, new libraries, breaking changes in what you import, and cyber tooling.
Leaves out:Governance, SOC operations, and vendor launches with no developer surface.
AMOUNT
DETAIL
ORDER
This issue came out before editions were ranked, so it shows the Standard edition in issue order.
Horizon3 NodeZero is an autonomous security tool that continuously identifies and exploits vulnerabilities in networks to assess organizational risk.
Horizon3 NodeZero's biggest addition this window is Tripwires — automatically deployed decoy files and credentials that flag intruder interaction during pentests — alongside expanded Rapid Response exploit coverage, Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. detection improvements, and MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface., MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs., and Vulnerability Management Hub upgrades.
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
NodeZero Tripwires decoy files and credentialsnew75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
NodeZero automatically deploys decoy files and credentials — up to two tripwires per asset — along critical attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. during autonomous pentests, placed at points where NodeZero has gained access via a Remote Access Tool (RAT) or direct file write; any interaction triggers an immediate alert. Tripwires are included in NodeZero Elite and Pro license packages and available as an add-on for other tiers. A subsequent update introduced more-flexible Tripwire deployment that reduces reliance on the RAT, cutting Endpoint Detection and Response (EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device.) noise during deployments.
Expanded Rapid Response exploit coveragenew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Rapid Response exploitability testing now covers Cisco Unified Communications Manager, SonicWall SMA1000, Adobe ColdFusion, and ManageEngine ADAudit Plus, viewable via Rapid Response Details pages showing Asset Breakdown, CVE or H3 IDs, References, and a Relevant Assets table with Action Items and Fix Actions guidance, plus a Take Action menu to run tests, add notes, or create tickets.
— Names covered products and UI actions, no API detail.snapshot-20260806
thinner coverage below
0300
Tripwires dashboard in NodeZero Portalnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
A Tripwires dashboard in the NodeZero Portal, opened from the portal's top navigation, gives visibility into deployed tripwires across the environment.
— Names exact UI path but no further behaviour detail.product docs
0400
Vulnerability Management Hub port info and sortingimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The Vulnerability Management Hub adds port information and improved sorting for completed pentests.
— Names the hub and new fields but no navigation steps.snapshot-20260806
0500
Active Directory group and DCSync detection improvementsimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Active Directory enhancements improve group enumeration, NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent. posture assessment, and DCSyncDCSyncAn attack that abuses Active Directory replication permissions to request password-related data from a domain controller. It imitates the synchronization normally performed between controllers. detection.
— Names three capabilities but no mechanism or scope detail.snapshot-20260806
0600
MSP contract, asset, and co-branding controlsimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
MSP enhancements strengthen contract enforcement, asset allocation, and co-branding controls for managed service providermanaged service providerA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. environments.
— Names three MSP controls without configuration or UI detail.snapshot-20260806
0700
MCP Server authentication and toolset updatesimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
MCPMCPModel 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 updates deliver stronger authentication, a streamlined toolset, and expanded documentation for safer integrations.
— Vague on what auth or toolset changes actually entail.snapshot-20260806
Subfinder v2.15.0 adds a new passive discovery source and machine-readable output for listing supported sources.
└──▷ WHAT SHIPPED ·
2 FEATURES0 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Machine-readable source listing via -ls -oJnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Running subfinder -ls -oJ outputs the available passive sources in JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. format, useful for feeding into automation or auditing which sources subfinder supports.
Get a machine-readable list of all available passive sources to feed into automation or audit which sources subfinder supports.
$ subfinder -ls-oJ
— Exact flag and output format given, with runnable example.v2.15.0
0200
New shodanct passive sourcenew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds shodanct as a new passive subdomain discovery source, leveraging Shodan's certificate transparency data; can be invoked with subfinder -d example.com -s shodanct.
Run subdomain enumeration using only the new shodanct source to leverage Shodan's certificate transparency data.
$ subfinder -d example.com -s shodanct
— Named source and exact command shown, mechanism briefly noted.v2.15.0
Snyk is a developer security platform that finds and fixes vulnerabilities in open source dependencies and container images.
Snyk added NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent. v2 authentication support for Web targets in Snyk API & Web, allowing authenticated DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. scans of Windows-protected internal applications.
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
NTLM v2 authentication for Web targetsnew83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Snyk API & Web now supports NTLM v2 authentication for Web targets, configurable via Target Settings > Authentication tab in the Basic Auth / NTLM module, with fields for username, password, domain, and workstation. This enables authenticated scans of Windows-protected internal applications without separate tooling.
Enable authenticated scanning of a Windows NTLM-protected internal application that was previously unscanned.
📍In the Snyk web UI, go to Target Settings › Authentication tab, locate the Basic Auth / NTLM module, select the NTLM option, and enter the username, password, domain, and workstation credentials for the target application.
Portkey is an AI gateway providing observability, security, and reliability features for LLM applications with multi-model support.
Portkey's March 2026 release adds vault-backed Secret References, weekly and endpoint-scoped rate limits, cross-cloud GCS logging via GCP Workload Identity Federation, new Zscaler and Akto guardrail integrations, and expanded model/provider support including DeepInfra, DeepSeek, Bedrock, Vertex AI, and Azure AI Foundry rerank.
└──▷ WHAT SHIPPED ·
3 FEATURES2 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Weekly rate-limit budgetsnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds weekly (rpw) budget and usage windows so rate-limit caps align with weekly spend planning, not only per-minute or monthly aggregates.
— Names the `rpw` unit but no config path or command.snapshot-20260806
0200
Analytics for archived workspaces and slug filtersimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Enables analytics for archived workspaces and accepts workspace slugs (alongside IDs) in saved filters, keeping reporting stable as workspaces are wound down or renamed.
— Describes behaviour but no filter syntax or API path.snapshot-20260806
0302
Removal of forwarded header to prevent loopsbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
The gateway no longer forwards the x-portkey-forward-headxers header, preventing header-forwarding loops; any setup relying on that header being passed through will stop working.
— Names the removed header but no migration path given.snapshot-20260806
└──▷ BREAKING ON UPGRADE
!
The gateway no longer forwards the x-portkey-forward-headxers header, preventing header-forwarding loops — any setup relying on that header being passed through will stop working.
Openlayer is a platform for monitoring and evaluating large language model performance, quality, and safety in production.
Openlayer shipped a Gantt-style trace timeline view that visualizes span timing and nesting to help spot slow steps and unexpected branches.
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Gantt-style trace timeline viewnew45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
A new trace timeline view lines up every span by start time, duration, and nesting so slow steps and unexpected branches are immediately visible at a glance.
— Describes behavior but no navigation path or config named.snapshot-20260806
Veracode is a cloud-based application security platform that performs static, dynamic, and software composition analysis to identify vulnerabilities.
Veracode expanded its EASMEASMExternal Attack Surface Management: a discipline and category of tooling that continuously discovers and monitors an organization's internet-facing assets to identify exposures before attackers do. module with real-time scan notifications, AI-powered risk prioritization, scan scheduling, and a new DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. Candidate export path into DAST Essentials, while its training platform shipped Get Lesson Progress API enhancements, OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. content, and deeper Security Labs integration into the Veracode Platform via IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access..
└──▷ WHAT SHIPPED ·
25 FEATURES7 OF 25 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Get Lesson Progress API enhancementsimproved95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds updatedAfter parameter to support incremental loads of lesson progress data and excludeNotStarted=true to filter out lessons that have not been started. The response now also includes stack and updated_on fields, and surfaces Not Started status when both start_time and end_time are null.
Security Labs default URL changebreaking80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
The default Security Labs URL changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. with a stand-alone account must update their configured URL.
OWASP Top 10:2025 Security Labs lessonsnew60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
New Security Labs lessons cover all ten OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10:2025 categories, including two new categories: A03 (Software Supply Chain Failures) and A10 (Mishandling of Exceptional Conditions).
OWASP Top 10:2025 eLearning coursesnew60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
New eLearning courses aligned to OWASP Top 10:2025 are available in English, Spanish, French, Portuguese, and Chinese, covering Software Security Awareness and secure coding for .NET, Java, JavaScript, PHP, and Python.
eLearning skills assessment quizzesnew60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
New assessment quiz courses (skills assessments) are available in English, Portuguese, and Spanish for Static Analysis, Dynamic Analysis, SCASCASoftware 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. agent-based scanning, IDE scanning, and user/application setup.
CWE tagging on Security Labs lessonsnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds CWECWECommon Weakness Enumeration, a catalog of recurring software and hardware weakness types. It describes classes of mistakes, such as injection, rather than individual vulnerability instances. tagging to Security Labs lessons, enabling admins to search lessons by CWE and learners to see which CWEsCWEsA community-maintained list of software and hardware weakness types, maintained by MITRE, that gives cyber tools a standard taxonomy for classifying and communicating vulnerability root causes. a lesson addresses.
Security Labs terminology renamebreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation, automation, or integrations referencing these terms must be updated.
33 deprecated eLearning courses removeddeprecated55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 2021, and language-specific Secure Coding courses for .NET, Java, JavaScript, PHP, and Python) are no longer available as of June 10, 2026. OWASP Top 10 (2021) Security Labs lessons are also no longer available as of that date.
In-app guidance for campaigns and reportingnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
New in-app guidance in Security Labs for creating campaigns and using reporting; requires third-party cookies enabled in Chrome, Edge, Firefox, Safari, and Internet Explorer 9+.
Container Security in Docker lesson seriesnew48how completely this was documenteddepth20/40specificity20/30actionability8/3048 / 100
New Security Labs lesson series on Container Security in Docker, covering capabilities, users, virtualization, networking, resources, and inventory across dozens of hands-on lessons.
The default Security Labs URL has changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSO with a stand-alone account must update their configured URL.
!
In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation, automation, or integrations referencing these terms must be updated.
!
The Security Labs community edition will be deprecated on July 31, 2026.
!
33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 2021, and language-specific Secure Coding courses for .NET, Java, JavaScript, PHP, and Python) are no longer available as of June 10, 2026.
!
OWASP Top 10 (2021) Security Labs lessons are no longer available as of June 10, 2026.
A next-generation crawling and spidering framework.
Katana v1.7.0 expands its knowledge base with secrets and endpoint extractors, adds content similarity deduplication to cut near-duplicate pages, and opens up headless engine callbacks with a Context field for external lifecycle control.
└──▷ WHAT SHIPPED ·
5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Content similarity deduplication of crawled pagesnew100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
The -pcs / -page-content-similar flag (also aliased as -sdd / -similarity-deduplication) enables Layer-2 content similarity filtering to deduplicate near-identical pages during crawls. Mode is set via -pcsm / -page-content-similar-mode (simhash, tfidf, or bm25; default simhash), tuned with -pcsd / -page-content-similar-distance (SimHash max Hamming distance, default 3), -pcst / -page-content-similar-threshold (TF-IDF/BM25BM25The classic keyword-ranking formula behind traditional search engines. Hybrid search combines it with embedding similarity so exact terms and meaning both count. min score 0–1, default 0.85), and -pcsn / -page-content-similar-budget (pages fully processed per similarity cluster, default 1).
Crawl a target and skip near-duplicate pages using TF-IDF similarity scoring to reduce noise on large sites.
— Full flag set with defaults and a runnable example.v1.7.0
0200
Secrets extractor in knowledge basenew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
The -kb-secrets flag enables a secrets extractor within the knowledge base that automatically detects exposed credentials and tokens during crawls. The -kb-validate-secrets flag validates detected secrets live against their respective providers by sending real API calls.
Crawl a target and extract secrets from the knowledge base, then validate them live against their providers.
— Named flags, mechanism, and runnable example given.v1.7.0
0300
Context field for lifecycle controlnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds a Context field to the Options struct for external lifecycle control — cancelling the provided context.Context stops the rate limiter, crawl session, queue, known-files requests, and headless browser.
— Named struct field with clear behaviour, no code sample.v1.7.0
0400
Endpoints extractor in knowledge basenew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
The -kb-endpoints flag enables an endpoints extractor that classifies REST, GraphQL, SOAP, and XHR requests found during crawling.
— Named flag and classification types, but no example.v1.7.0
thinner coverage below
0500
Headless engine callbacksnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Adds callbacks to the headless engine, enabling programmatic interception of headless browser events.
— Describes capability but no API names or usage shown.v1.7.0
GitGuardian Detection Engine scans code repositories to identify and alert on exposed secrets, credentials, and sensitive data in real-time.
GitGuardian's Detection Engine expanded its secret-detection coverage with eight new detectors (Lovable, Slack Workflow Builder, n8n, Atlassian, AWS Cognito, OpenAI, Vercel OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user., OpenCode) and a new Supabase JWTJWTAn open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. checker, while also tightening validation on GitHub, npm and PostgreSQL detectors and removing/disabling two detectors.
└──▷ WHAT SHIPPED ·
10 FEATURES0 OF 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
PostgreSQL credentials detector expanded matchingimproved70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
PostgreSQL credentials detectors now match usernames containing dashes (e.g. workflow-prod-user) and raise the username length bound from 20 to 30 characters.
New detectors for Slack, n8n, Atlassian and othersnew65how completely this was documenteddepth25/40specificity30/30actionability10/3065 / 100
Seven new detectors were added: Slack Workflow Builder webhook trigger URLs, n8n API keys, Atlassian auth keys (OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms.access tokensaccess tokensA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. issued by auth.atlassian.com), AWS Cognito User Pool access tokens, OpenAI platform access tokens, Vercel OIDC workload-identity tokens, and OpenCode API keys.
Azure Event Hub/Service Bus checker false-valid fiximproved65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Azure Event Hub and Azure Service Bus checkers now only report a key as valid when the 200 response is a genuine Service Bus Atom feed, blocking false-valid results behind intercepting proxies.
GitHub token detector format validationimproved50how completely this was documenteddepth20/40specificity25/30actionability5/3050 / 100
The GitHub Personal Access Token, GitHub OAuth Token, and GitHub App Token detectors now skip values that fail format validation, reducing false positives from generic detectors.
Supabase service_role JWT checkernew40how completely this was documenteddepth15/40specificity20/30actionability5/3040 / 100
A new checker validates Supabase service_roleJWTsJWTsJSON Web Tokens — an open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object. Cyber tools use them for stateless authentication without server-side session storage..
Sophos DNS Protection is a security service that blocks malicious websites and threats by filtering DNS queries at the network level.
Sophos DNS Protection adds a dedicated Generative AI web category, giving filtering policies granular control over AI services separate from other business categories.
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Generative AI filtering categorynew57how completely this was documenteddepth25/40specificity20/30actionability12/3057 / 100
A new Generative AI category is added to the Business and generative AI category group (formerly Business-relevant site categories), letting filtering policies block or allow generative AI websites independently of other business categories.
Fastly is a content delivery network and edge computing platform that accelerates website performance and provides security services globally.
Fastly's Next-Gen WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. now surfaces who created a given rule or signal, adding a created_by field to its API responses.
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
created_by field in Next-Gen WAF APIsnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
The Next-Gen WAF Rules API and Next-Gen WAF Signals API responses now include a created_by field, identifying the email address of the user who created the rule or signal.
Docker Sandboxes provides isolated, lightweight environments for securely running and testing AI models and applications with controlled dependencies.
Docker Sandboxes' v0.38.0 release adds local model routing for Claude Code, first-class MCPMCPModel 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 management, enterprise proxy/NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent./KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. support, per-sandbox network deny rules, and experimental GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference. passthrough, while accompanying docs detail a new AI Governance Audit Logs feature (0.35.0+) and OpenCode Zen API key integration.
└──▷ WHAT SHIPPED ·
15 FEATURES6 OF 15 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
OpenCode Zen API key custom secret with host proxy substitutionnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
sbx secret set-custom -g --host opencode.ai --env OPENCODE_API_KEY --value stores OpenCode Zen API keys so the real key stays in the host secret store while the sandbox receives a placeholder that the host-side proxy substitutes on requests to opencode.ai. Sandboxes also need sbx policy allow network opencode.ai:443 to reach the OpenCode Zen service.
Store an OpenCode Zen API key as a global custom secret so all OpenCode sandboxes can authenticate to opencode.ai without exposing the real key inside the sandbox.
Allow an OpenCode sandbox to reach the OpenCode Zen API over HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. after adding the custom secret.
$ sbx policy allow network opencode.ai:443
— Exact runnable commands and mechanism givenproduct docs
0201
AI Governance Audit Logs with local and cloud deliverynew85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Requires Docker Sandboxes 0.35.0+ and an AI Governance subscription. The sandbox daemon writes local audit records as .jsonl.jsonlA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. files (JSON Lines) to per-OS paths — ~/Library/Logs/com.docker.sandboxes/sandboxes/auditkit/ (macOS), ${XDG_STATE_HOME:-~/.local/state}/sandboxes/sandboxes/auditkit/ (Linux), %LOCALAPPDATA%\DockerSandboxes\sandboxes\logs\auditkit\ (Windows) — named audit-<utc-timestamp>-<process-uuid>-<seq>.jsonl, finalized by atomic rename at rotation thresholds of 5 minutes, 1000 events, or 50 MiB. Records include evaluation events (resource, action, verdict, deny_reason) and session lifecycle events linked by audit_session_id, with fields like audit_event_id, schema_version, username, org_id, hostname, network_egress. Local delivery supports SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. ingestion via log shippers (Splunk Universal Forwarder, Filebeat, CrowdStrike Falcon LogScale); Docker Cloud delivery (on by default when AI Governance is enabled) additionally powers a hosted audit log view, CSV export, and SIEM streaming from app.docker.com, configurable by org owners or custom-role users. Run sbx policy ls to confirm a Governance: Managed by <org> line, a prerequisite for audit records to be written.
Confirm that governance is active and audit logging is enabled before relying on local audit records.
$ sbx policy ls
— Full field/path/rotation detail plus one verification command, no enable stepsproduct docs
0300
Local model routing for Claude Codenew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
sbx run --model <name> claude serves a local GGUFGGUFThe single-file model format used by llama.cpp and Ollama, holding the weights, usually quantized, together with the tokenizer and settings needed to run the model locally. model via llmman, or an already-running Ollama install using an ollama/ prefix, routing Claude Code away from api.anthropic.com. Requires enabling sbx settings set platform.allowExperimentalFeatures true and sbx settings set feature.model true first.
Route Claude Code at a local GGUF model instead of api.anthropic.com — useful for air-gapped or cost-sensitive environments.
$ sbx settings set platform.allowExperimentalFeatures true
sbx settings set feature.model true
sbx run --model llama3.2 claude
— Exact commands and enabling flags providedv0.38.0
0400
Enterprise proxy support with NTLM/Kerberos and TLS optionsnew85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Settings-driven upstream-proxy configuration via proxy, proxy.sandbox, proxy.daemon, and matching no_proxy keys defaults to the host OS system proxy and proxies daemon traffic (image pulls, telemetry) too. proxy.integratedAuth enables NTLM/Kerberos/Negotiate proxy authentication on Windows, and tls.allowNegativeSerial supports TLS-inspecting proxies issuing certificates with negative serial numbers. Blocked HTTPS proxy connections now appear in sbx policy log even when the client aborts the TLS handshake.
Configure a corporate HTTPS proxy for all sandbox and daemon traffic with NTLM authentication on Windows.
$ sbx settings set proxy http://proxy.corp.example.com:8080
sbx settings set proxy.integratedAuth true
— Named settings keys with a runnable configuration examplev0.38.0
0502
Per-sandbox network deny rulesnew65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
--deny-network HOST flag on sbx run and sbx create records per-sandbox egress deny rules at creation time, e.g. to block a sandbox from reaching a specific host to prevent exfiltration.
Block a sandbox from reaching a specific host at creation time, e.g. to prevent exfiltration to an external service.
First-class MCP server management with live index refreshimproved60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
sbx mcp becomes a first-class, no-longer-hidden subcommand for MCP server management, with sbx mcp add supporting --dir and OAuth override flags; registering a server immediately refreshes the mcp-find/mcp-add index in every running sandbox without recreating them. Dynamic MCP tools mcp-find, mcp-add, and mcp-config-set are now also available in local sandbox mode.
— Named subcommand and flags but no worked examplev0.38.0
0704
Experimental NVIDIA GPU passthroughnew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
sbx run --gpu (experimental) enables NVIDIA VFIOVFIOA Linux kernel framework that lets userspace programs take direct ownership of a PCI device, bypassing kernel drivers, giving cyber tools low-latency, isolated hardware access without running in kernel space. GPU passthrough on Linux; enable with sbx settings set feature.sandbox-gpu true.
— Named flag and enabling setting, no worked walkthroughv0.38.0
thinner coverage below
0800
sbx mount host bind-mount at matching pathimproved55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
sbx mount <sandbox> <host> now bind-mounts the host path at the same path inside the sandbox when no container target is given; :ro mounts are enforced read-only at the virtio-fs host edge.
— Behaviour and enforcement point described, no examplev0.38.0
0905
Secrets default to global scopebreaking50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Service and custom secrets are now global by default, with a --sandbox flag for sandbox-scoped secrets; legacy positional and --global forms are deprecated with warnings.
— Names flag and deprecation but no migration examplev0.38.0
1006
sbx mcp bundle command removedbreaking40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The sbx mcp bundle command has been removed; single-server management via sbx mcp add/ls/rm is now the only supported flow.
— States removal and replacement, no migration stepsv0.38.0
1100
sbx daemon restart commandnew40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
sbx daemon restart stops and restarts the sandboxd daemon in the background.
— Command named but no further mechanism describedv0.38.0
1200
Claude Vertex multi-region endpoint supportimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Claude Vertex sandboxes now support us and eu multi-region endpoints.
— Names regions but no configuration steps givenv0.38.0
1300
Configurable cloned workspace volume sizenew35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
DOCKER_SANDBOXES_CLONED_WORKSPACE_SIZE environment variable configures the size of the cloned workspace volume.
— Env var named, no default or usage example givenv0.38.0
1400
Homebrew stapled .dmg installer on macOSimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Homebrew installs now use a stapled .dmg artifact instead of a .tar.gz archive, improving Gatekeeper compatibility on macOS.
— Names artifact change, nothing for the reader to runv0.38.0
1500
sbx inspect shows custom secretsimproved30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
sbx inspect now displays custom secrets configured for a sandbox.
— Single-line change with no further detailv0.38.0
└──▷ BREAKING ON UPGRADE
!
The sbx mcp bundle command has been removed; single-server management via sbx mcp add/ls/rm is the only supported flow.
!
Service and custom secrets default to global scope; legacy positional and --global forms are deprecated with warnings.
OpenShell is the safe, private runtime for autonomous AI agents.
OpenShell v0.0.99 adds a system CA root mode for sandboxes, starts honoring OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. image working directories, and fixes a TCP_NODELAY latency issue.
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
System CA root mode for sandboxesnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds a system CA root mode to the build, enabling sandboxes to trust the host's system certificate authorities.
— Names the capability and effect but no flag or config surface given.v0.0.99
0200
TCP_NODELAY latency fiximproved30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
The release includes a latency fix related to TCP_NODELAY, though no further explanation of the change is given.
— Names the socket option but lacks context on scope or impact.v0.0.99
0300
Honors OCI image working directoriesimproved25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
OpenShell now honors the working directory specified in OCI images, per the release summary; no further mechanism is described.
— Only mentioned briefly in the summary, no detail on behavior.v0.0.99
Code signing and transparency for containers and binaries
cosign v3.1.3 adds support for signing OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. images with an X.509X.509A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. certificate chain and auto-detects digest algorithms for public keys.
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
OCI signing with X.509 certificate chainnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
cosign now supports OCI signing with an X.509 certificate chain, enabling bring-your-own PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. workflows for container image signing.
— Names capability but no flag or command shown.v3.1.3
0200
Auto-detected digest algorithm for public keysimproved40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
cosign auto-detects the default digest algorithm for public keys, removing the need to manually specify it.
— Describes behaviour change but no flag or command detail.v3.1.3
Prowler is the Open Cloud Security Platform trusted by thousands to automate security and compliance in any cloud environment. With thousands of ready-to-use checks and compliance frameworks, delivers real-time, customizable monitoring and seamless integrations, making cloud security simple, scalable, cost-effective for organizations of any size.
Prowler 5.38.0 expands M365 compliance coverage with 12 new checks, adds 20 AWS privilege-escalation Attack Paths queries plus outcome-category metadata, and introduces Compliance Watchlists and multi-domain SAML SSOSAML SSOAn authentication protocol that lets a user log in once with an identity provider and access multiple services without re-entering credentials, by passing signed XML assertions between parties. in Prowler Cloud/Private Cloud.
└──▷ WHAT SHIPPED ·
10 FEATURES0 OF 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
New M365 checks for CIS Foundations Benchmark v7.0.0new85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds 12 M365 provider checks: admincenter_shared_bookings_disabled (control 1.3.9); defender_priority_account_protection_enabled and defender_strict_preset_security_policy_enabled (controls 2.4.1, 2.4.2); exchange_owa_mailbox_policy_personal_accounts_disabled and exchange_organization_reject_direct_send_enabled (controls 6.3.2, 6.5.5); teams_external_access_trial_tenants_blocked (control 8.2.4); and six device-registration checks — entra_device_registration_join_restricted, entra_device_registration_max_devices_per_user_limited, entra_device_registration_global_admins_not_local_admins, entra_device_registration_registering_user_not_local_admin, entra_device_registration_laps_enabled, and entra_policy_default_user_cannot_read_bitlocker_keys (controls 5.1.4.x), all mapped to CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. Microsoft 365 Foundations Benchmark v7.0.0.
— Named checks and exact CIS control mappings given5.38.0
0200
20 new AWS privilege-escalation queries in Attack Pathsnew80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Attack Paths adds 20 AWS privilege-escalation detection queries sourced from pathfinding.cloud, covering iam:PassRole escalations across AWS Batch, Braket, Cognito Identity, ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping., EMR, EMR Serverless, GameLift, Glue, EC2EC2Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. Image Builder, Kinesis Analytics, HealthOmics, EventBridgeEventBridgeAWS's managed event bus service that routes events between cloud services, SaaS apps, and custom code using rules and targets, letting tools react to state changes without polling or managing message infrastructure. Scheduler, SSM, and Step Functions, plus CodeDeploy/Step Functions existing-resource abuse, permissions-boundary removal with role assumption, and IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. Identity Center permission-set policy injection.
— Detailed services and escalation paths, no direct usage step5.38.0
0300
Outcome category on Attack Paths query metadataimproved70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Attack Paths query metadata now exposes an outcome category (Code execution, Privilege escalationPrivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., Public exposure, or Resource inventory) on the queries endpoint, enabling terminal outcome nodes in the graph.
— Names the endpoint and category values but no path/method5.38.0
0400
Expanded privilege-escalation combinations in IAM policy checkimproved65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
— Named check and services covered, but no run instructions5.38.0
0500
Multi-domain SAML SSO configurationimproved65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider.SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. now supports one primary email domain plus up to 19 additional domains under a single Identity Provider configuration and a single stable ACS URL (Prowler Cloud/Private Cloud).
— Exact domain limit and ACS URL detail, no config path5.38.0
thinner coverage below
0600
Compliance Watchlist for pinned frameworksnew55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Compliance Watchlist (Prowler Cloud/Private Cloud) lets teams pin frameworks from any compliance view, filter the Compliance section to pinned frameworks only, and see pinned framework scores on the Overview page.
— Describes behaviour and UI location, no config key5.38.0
0700
Sign-in method tags in Users tablenew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Users table in Prowler Cloud now shows each account's sign-in methods as tags, including email/password, Google, GitHub, SAML with linked domains, and Partner SSO.
SBOMs and build-provenance attestations for container imagesnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Prowler API, UI, SDK, and MCPMCPModel 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. container images now publish per-architecture SBOMsSBOMsA 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 build-provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build. attestations as OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. attestations.
— Names artifacts and format but no retrieval command5.38.0
0900
Grype scanning alongside Trivy in image security gatesimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Grype now runs alongside Trivy across container-image security gates, blocking on fixable high and critical findings.
— Names tools and gate behaviour, no config surface5.38.0
1000
Checksum verification for downloaded build binariesimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
API and SDK container builds now verify checksums of downloaded PowerShell, Trivy, and zizmor binaries before installation.
— Names binaries but process is internal, not user-actionable5.38.0
Wiz is a cloud security platform that identifies and remediates risks across cloud infrastructure and applications.
Wiz added automated DISA STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against. compliance assessment for Amazon Linux 2023 and Windows Server 2025 in AWS GovCloud, closing gaps where official SCAP content isn't yet available.
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Automated DISA STIG assessment for AL2023 and Windows Server 2025new68how completely this was documenteddepth30/40specificity28/30actionability10/3068 / 100
Wiz adds automated DISA STIG compliance assessment covering Amazon Linux 2023 (AL2023 V1R2 and V1R3 benchmarks) and Windows Server 2025, filling gaps where official SCAP content is not yet available. It delivers continuous hardening validation for federal agencies and defense contractors operating in AWS GovCloud, supporting FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. Rev5, FedRAMP 20xFedRAMP 20xA GSA-led overhaul of the FedRAMP cloud-authorization program aimed at cutting compliance burden through continuous, automated evidence collection rather than point-in-time audits, letting vendors reach federal markets faster., CMMC, and DoD authorization requirements.
— Names benchmarks and frameworks but no config or API surface given.2026-08-06-c676879b
Wiz Cloud is a cloud security platform that identifies and remediates risks across cloud infrastructure, applications, and data.
Wiz added automated DISA STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against. compliance assessment for Amazon Linux 2023 and Windows Server 2025, surfacing agentless host-level findings directly in the Compliance Posture dashboard.
└──▷ WHAT SHIPPED ·
6 FEATURES1 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
DISA STIG Amazon Linux 2023 assessment via HCRnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Adds DISA STIG Amazon Linux 2023 benchmark support via Host Configuration Rules (HCR), providing continuous agentless assessment across all connected cloud instances without SCAP content or scan credentials. Enable it in the Wiz portal under Compliance Posture > Manage Frameworks by searching for DISA STIG Amazon Linux 2023 — assessment begins automatically for all connected instances.
Enable the DISA STIG Amazon Linux 2023 framework to start continuous agentless assessment across your entire AL2023 fleet.
📍In the Wiz portal, go to Compliance Posture › Manage Frameworks, search for DISA STIG Amazon Linux 2023, and enable the benchmark — assessment begins automatically for all connected instances.
DISA STIG Windows Server 2025 assessment via HCRnew77how completely this was documenteddepth28/40specificity24/30actionability25/3077 / 100
Adds DISA STIG Microsoft Windows Server 2025 benchmark support via Host Configuration Rules (HCR), with an initial automated rule set and expanding coverage planned in upcoming releases. Enable it via Compliance Posture > Manage Frameworks by searching for DISA STIG Microsoft Windows Server 2025 — new instances are assessed automatically on deployment.
Enable the DISA STIG Microsoft Windows Server 2025 framework to continuously assess Windows Server 2025 hosts as they are deployed.
📍In the Wiz portal, go to Compliance Posture › Manage Frameworks, search for DISA STIG Microsoft Windows Server 2025, and enable the benchmark — new instances are assessed automatically on deployment.
— Exact portal steps given; rule set breadth unspecified.2026-08-06-d1ea617b
thinner coverage below
0300
STIG findings in Compliance Posture dashboardnew50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
STIG findings for both new frameworks surface in the Compliance Posture dashboard alongside existing frameworks, with per-rule pass/fail status per instance and rollup into category and subcategory scores.
— Describes rollup behaviour but no exact dashboard path.2026-08-06-d1ea617b
0401
Filter findings by STIG severity categorynew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Supports filtering findings by STIG severity category (CAT I, CAT II, CAT III) to prioritize high-impact failures.
Iru shipped three Apple device management updates: Apple beta program enrollment via the Software Update Library Item, phased rollout support extended to Managed OS updates, and Authenticated Guest Mode for Platform SSOPlatform SSOA macOS framework from Apple that lets identity providers hook into the operating system login flow, enabling enterprise single sign-on at the platform level rather than per-app. on macOS.
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Apple beta program enrollment via Software Update Library Itemnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
The Software Update Library Item now supports Apple beta program enrollment, allowing end users to opt-in or letting admins enforce a specific beta program without tying it to a specific version.
Phased rollouts for Managed OS updatesnew50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Extends phased rollout support — previously available for Mac Auto Apps — to Apple Managed OS, letting admins stage OS update declarations across their device fleet instead of pushing to all devices simultaneously.
Authenticated Guest Mode for Platform SSO on Macnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds Authenticated Guest Mode configuration support to the Single Sign-On Extension Library Item when using Platform SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. with macOS.
Tenzir is a security data platform that ingests, transforms, and analyzes security telemetry and threat intelligence data.
Tenzir's v6.9.0 release line adds native Apache IcebergApache IcebergAn open table format for large analytic datasets, maintained by the Apache Software Foundation, that gives cyber tools reliable schema evolution, time-travel queries, and atomic commits on object storage or HDFS. output, automatic NetFlow/IPFIXIPFIXAn IETF standard protocol for exporting network flow records from routers and probes to a collector, giving cyber tools a vendor-neutral stream of structured traffic metadata without full packet capture. decoding, and OCSF 1.9.0OCSF 1.9.0An open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format for security telemetry so cyber tools can share and ingest logs without custom normalization. schema support, alongside several new configuration keys for faster, lower-memory catalog startup and data-integrity validation.
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Native Apache Iceberg output via to_icebergnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
A new to_iceberg operator writes events directly into Apache Iceberg tables through a REST catalog, with mode (create_append, create, append), partition_by supporting hidden-partition transforms (year, month, day, hour, bucket, truncate), plus max_size, timeout, and buffer_size for file rotation. It writes zstd-compressed Parquet with automatic schema evolution for heterogeneous streams, and connects to S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. stores via aws_iam, s3_endpoint, s3_path_style, bearer-token catalogs via token, AWS Glue/Amazon S3 Tables via catalog_aws_service, and Google BigLake via gcp_service_account_key or gcp_auth.
Write a live OCSFOCSFAn open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format so cyber tools can share and ingest log data without per-source normalization work. stream to an Iceberg table partitioned by class and day, with automatic schema evolution.
Faster catalog startup via index tuning config keysnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
New config keys reduce startup time and memory on nodes with many partitions: tenzir.index.load-concurrency tunes worker threads for concurrent partition synopsis loading (defaults to hardware concurrency); tenzir.index.lazy-sketches defers Bloom-filter sketch loading to query time, bounding warm memory via an LRU cache sized by tenzir.index.sketch-cache-bytes (default 1 GiB); and tenzir.index.skip-synopsis-verification skips recursive FlatBuffers verification of partition synopses at startup, trading corruption robustness for speed on trusted networked storage such as NFS.
Reduce startup memory and load time on a node with many partitions backed by NFS.
Reduce startup memory and time on a node with many partitions by deferring Bloom-filter sketch loading and skipping synopsis verification on trusted NFS storage.
Automatic NetFlow and IPFIX decodingnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
A new read_netflow operator automatically decodes NetFlow v5, NetFlow v9, and IPFIX from byte streams and UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. envelopes in a single pipeline, learning templates per exporter and preserving unknown elements as blobs, with no manual parser configuration or protocol pre-selection needed.
Ingest mixed NetFlow v5/v9 and IPFIX from UDP on port 2055 in a single pipeline.
Store batch validation for corruption diagnosisnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
The tenzir.validate-store-batches config key fully validates every Arrow record batch read from a persisted Feather store, helping diagnose on-disk corruption including malformed UTF-8; disabled by default.
Faster ocsf::cast variant encoding and null-fillingimproved60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
ocsf::cast with encode_variants=true now encodes free-form objects such as unmapped significantly faster, lowering CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. usage for high-volume streams, and ocsf::cast with null_fill=true now uses significantly less memory and CPU by avoiding per-batch column rebuilds.
Dynamic field assignment with expression keysnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Fields can now be assigned using expression keys via result[key] = value, letting field names be determined per-event at runtime instead of being fixed at pipeline-definition time.
A secure low code deception runtime framework, leveraging AI for System Virtualization.
Beelzebub v3.9.0 shifts plugin management to declarative YAML configuration, adds boot-time background plugins, and introduces shared JSON Schema validation for honeypot configs.
└──▷ WHAT SHIPPED ·
4 FEATURES0 OF 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
ServicePlugin background plugins at bootnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds ServicePlugin support for background plugins that start automatically at boot time.
— Names concrete plugin type but no usage stepsv3.9.0
0200
Shared JSON Schema validation for honeypot configsnew43how completely this was documenteddepth20/40specificity15/30actionability8/3043 / 100
Adds shared JSON Schema validation for honeypot configurations, catching config errors before deployment.
— Names format and benefit, lacks schema location or commandv3.9.0
0300
YAML-based plugin declarationsimproved33how completely this was documenteddepth15/40specificity10/30actionability8/3033 / 100
Plugin declarations move to YAML config files, enabling declarative plugin management via configuration files instead of the prior approach.
— Names config format but no key or file path givenv3.9.0
0400
Improved installer experienceimproved5how completely this was documenteddepth5/40specificity0/30actionability0/305 / 100
Sumo Logic is a cloud-based monitoring and analytics platform for logs, metrics, and security data.
Sumo Logic added Mobot, a chat-based assistant that builds and edits Automation Service playbooks from natural-language descriptions.
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Mobot natural-language playbook creationnew60how completely this was documenteddepth30/40specificity15/30actionability15/3060 / 100
Mobot supports playbook creation and editing via natural-language chat: you describe the automation you want, Mobot checks available integrations, asks clarifying questions, proposes a plan, configures each step, and saves the result as a draft for review and publishing.
Feedly Threat Intelligence aggregates security feeds and threat data to help organizations monitor emerging cybersecurity threats and vulnerabilities.
Feedly's Vulnerability Intel Agent added a dedicated Atlassian security release filter with product, attack-path, and patch-policy filtering, alerting, and expanded vendor advisory coverage.
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Attack path filtering for CVEsnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
CVEs can be filtered by attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. — attack vector, privileges required, and user interaction — to isolate unauthenticated, no-interaction reachable vulnerabilities.
Patch policy threshold filtering (CVSS/EPSS)new65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Filtering by patch policy thresholds supports CVSSCVSSCommon 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 cutoffs, EPSSEPSSExploit 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. probability cutoffs, or both combined, letting teams isolate CVEs that breach both thresholds simultaneously to match internal patch policies.
Latest Atlassian Security Release filternew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
A Latest Atlassian Security Release filter in the Vulnerability Intel Agent always points to the most recent Atlassian advisory, ingested within minutes of publication, eliminating the need for manual updates each cycle.
Product-level CVE filtering for Atlassian stacknew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Filtering supports scoping Atlassian CVEs down to specific products in a team's stack, such as Confluence Data Center, Sourcetree, and Jira, to surface only relevant exposures.
Configurable enrichment columns in output tableimproved35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Enrichment columns in the Vulnerability Intel Agent's output table are reorderable and individually showable or hidable to match team triage workflows.
Tenable is a cybersecurity platform that identifies, measures, and remediates vulnerabilities across an organization's entire attack surface.
Tenable introduced Hexa AI, an agentic capability within Tenable One that automates exposure remediation end-to-end using intent-driven Routines and human-approval guardrails.
└──▷ WHAT SHIPPED ·
3 FEATURES2 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Intent-driven Routines for remediation workflownew55how completely this was documenteddepth30/40specificity15/30actionability10/3055 / 100
Routines encode the multi-step remediation workflow — asset scoping, policy targeting, patch execution, status check, and re-scan confirmation — into a single automated sequence triggered by intent.
— Lists workflow steps but no exact command or config to invoke2026-08-05-bfc66599
0202
Tenable Hexa AI agentic remediationnew48how completely this was documenteddepth25/40specificity15/30actionability8/3048 / 100
Tenable Hexa AI is an agentic capability within Tenable One that automates the full remediation cycle — scoping, patch deployment, and verification — across integrated platforms such as Jamf.
— Describes scope and integration but no config or API surface2026-08-05-bfc66599
0300
Human approval guardrails on AI autonomynew35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
AI autonomy is bound strictly to defined user permissions within the Tenable One harness, with human approval gates required before changes are applied.
— Explains safety mechanism conceptually, no configurable permission details given2026-08-05-bfc66599
Tenable One is an integrated cybersecurity platform that unifies vulnerability management, cloud security, and compliance across an organization's entire attack surface.
Tenable One introduces Tenable Hexa AI, an agentic engine that turns natural-language objectives into gated, end-to-end vulnerability remediation routines.
└──▷ WHAT SHIPPED ·
6 FEATURES4 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Natural-language intent-driven routines with guardrailsnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Intent-driven routines let practitioners define an objective, guardrails (e.g., 'Never launch a credentialed scan against anything tagged OT,' 'Open no more than twenty-five tickets in a run'), and a cadence (on-demand or scheduled) in plain natural language — no scripts required.
— Concrete guardrail examples give a clear starting point2026-08-05-1fa9e5be
0202
Proposal-gated execution before changesnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Before writing any changes, Hexa presents a plan showing device count, device list, policy, deployment window, and blast radius, and requires explicit approval before proceeding.
— Detailed plan fields but no exact command to trigger it2026-08-05-1fa9e5be
thinner coverage below
0303
Hexa AI agentic remediation enginenew55how completely this was documenteddepth30/40specificity15/30actionability10/3055 / 100
The new Tenable Hexa AI agentic engine automates end-to-end vulnerability remediation within a single conversational workflow — enumerating affected assets, mapping CVEs to fix versions, and executing patch deployments without manual tool-switching.
Mid-workflow scope narrowingnew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Supports scope narrowing mid-workflow — tell Hexa to restrict enumeration to a single business unit and it re-scopes and returns a revised plan before executing.
— Describes behavior with a concrete example but no exact syntax2026-08-05-1fa9e5be
0500
Routines adapt to infrastructure changesimproved35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
Routines adapt automatically to infrastructure changes such as new asset classes, renamed tags, or failed scans, without requiring script updates.
iDenfy is an identity verification platform that performs KYC/AML checks through document scanning and biometric analysis for compliance.
iDenfy's headline shipment this window is Age Estimation — a selfie-only age-gating capability with automatic document step-up, webhook delivery, and a full dashboard for session configuration and review — alongside new Bank Verification, Face Authentication, Fraud Prevention, AMLAMLAnti-Money Laundering: a set of laws, regulations, and procedures that financial institutions must follow to detect and report suspicious financial activity; cyber tools use it to automate transaction monitoring and compliance workflows. Screening and KYBKYBKnow Your Business — a regulatory compliance process for verifying the legal identity, ownership, and legitimacy of a business entity, used by cyber tools to screen counterparties or customers against fraud and sanctions risk. APIs, plus a long tail of KYB/IDV language, workflow, billing, and SDK improvements.
└──▷ WHAT SHIPPED ·
44 FEATURES6 OF 44 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Age Estimation session management dashboardnew96how completely this was documenteddepth38/40specificity30/30actionability28/3096 / 100
New Age Estimation section in the dashboard for browsing, filtering, searching and inspecting sessions, with a New estimation form exposing Minimum age (1–120), Safety margin (0–20 years), ID verification for uncertain results, Retry limit (1–3), Save selfie photo, and Link expiry time across General settings and Verification redirects tabs. Supports a per-session Webhook URL override and per-outcome redirect URLs (Success, Underage, Uncertain); the session list groups results into Results, Needs Attention, In Progress, Expired with filtering by client ID/creation date and search by session ID or client reference; session detail view surfaces a Step-up link to the underlying identity verification. Step-up Document Scans bill from Age Estimation finances rather than counting against document scan usage; viewing requires the View age estimation data permission and creating sessions requires MANAGE_AGE_ESTIMATION.
— Exact config keys, ranges, permission names and nav givensnapshot-20260806
0201
Age Estimation capability, API and webhooksnew83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
Selfie-only minimum-age check that avoids a document scan in the common case; triggers an automatic document step-up to read an exact date of birth from the ID and compare the ID portrait against the capture selfie when the AI model lacks confidence. Session outcomes SUCCESS, UNDERAGE, UNCERTAIN, FACE_MISMATCH, ATTEMPTS_EXCEEDED are delivered via a signed Age Estimation Webhooks HTTP POST with idempotent delivery as soon as a session finishes; lifecycle statuses PENDING, PROCESSING, COMPLETED, FAILED, EXPIRED are returned by the Partner API, which pre-checks finances and rejects requests with 402 when funds are insufficient. Billed from a dedicated Age Estimation finances pool separate from standard KYCKYCKnow Your Customer — a regulatory requirement that financial services verify the identity of their users before granting access, used by cyber tools handling payments or financial data to stay compliant. charges.
Branded email templates for KYB workflowsnew77how completely this was documenteddepth30/40specificity25/30actionability22/3077 / 100
New Email template configuration under Business Verifications → Configurations → Email template lets teams create branded emails for three template types — a new business verification session URL, a renewed session URL requesting an information update, and a completed-company verification result — with an Add verification link action that inserts a session URL placeholder into the email body.
— Exact UI path and template types given, no API surfaceproduct docs
0402
KYB API for company verificationnew62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
New KYB API enables company verification via registry data retrieval, beneficial owner screening, and AML checks, with dashboard-based compliance reviews. A Stakeholder Roles reference documents five roles — CEO, Representative, Shareholder, UBOUBOuBlock Origin, a browser extension maintained by Raymond Hill that blocks ads and trackers using filter lists; cyber tools embed or reference it to strip unwanted content from web traffic or scraped pages., and ABO — including mappings for partnerships, foundations, and holding chains.
— Names roles and checks, no endpoint paths givenproduct docs
thinner coverage below
0503
Fraud Prevention APInew50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
New Fraud Prevention API adds AI risk scoring, VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. and proxy detection, phone validation, and address verification checks.
— Lists check types, no endpoint or scoring detailproduct docs
0604
AML Screening APInew50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
New AML Screening API supports sanctions, PEP, and adverse media checks, offered as single checks or ongoing monitoring.
— Lists check categories, no endpoint or configproduct docs
0700
Android SDK screenshot blocking, camera detection, and 3D livenessimproved50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Android SDK 8.7.1 adds screenshot blocking and virtual camera detection; Android SDK 8.7.6 adds optional 3D liveness and reduces SDK size.
Bank Verification APInew47how completely this was documenteddepth20/40specificity15/30actionability12/3047 / 100
New Bank Verification API verifies customer bank accounts and financial information programmatically, with session creation and webhook callbacks.
— Describes flow and webhook, no endpoint pathproduct docs
0906
Face Authentication APInew47how completely this was documenteddepth22/40specificity15/30actionability10/3047 / 100
New Face Authentication API supports biometric face matching to re-authenticate returning users during account login, high-risk actions, and periodic checks.
— Names use cases, no endpoint or session modelproduct docs
1000
Tax identification fields in KYBnew41how completely this was documenteddepth15/40specificity18/30actionability8/3041 / 100
Dedicated tax identification fields — VAT Number, EIN, TIN — added to KYB workflows.
KYC API documentation for document checks and reviewimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Identity Verification (KYC) API documentation now covers document checks, liveness detection, and AI plus human review.
— Documentation scope only, no new mechanism describedproduct docs
2100
New Digital ID support: Austrian Handy Signatur, Freja eID, Mobile IDnew30how completely this was documenteddepth12/40specificity15/30actionability3/3030 / 100
New Digital ID support added: Austrian Handy Signatur, Freja eID, Mobile ID (Sprint 126).
iOS SDK NFC improvementsimproved27how completely this was documenteddepth10/40specificity12/30actionability5/3027 / 100
iOS SDK 8.7.7 adds NFCNFCNear Field Communication, a short-range (≤4 cm) wireless standard maintained by the NFC Forum, enabling data exchange between devices; cyber tools use it to probe, emulate, or intercept contactless card and tag transactions. improvements.
SMS verificationnew21how completely this was documenteddepth8/40specificity8/30actionability5/3021 / 100
SMSSMSShort Message Service, the protocol built into cellular networks for sending text messages between phones; cyber tools use it for alerting, two-factor authentication delivery, or phishing simulation over mobile channels. verification added (Sprint 123).
Arabic language and RTL support for IDVnew21how completely this was documenteddepth8/40specificity10/30actionability3/3021 / 100
Arabic language and RTLRTLRegister Transfer Level, a hardware design abstraction describing how data moves between registers each clock cycle; cyber tools use it to analyze or synthesize digital circuits from HDL source. support added to IDV (Sprint 127).
Clerk is a user authentication and identity management platform that provides sign-up, login, and user profile management for web and mobile applications.
Clerk added Device Trust to require a second factor on new-device password sign-ins, introduced Google Workspace Directory Sync with role mapping, and published community-maintained Flutter integration docs.
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Google Workspace Directory Syncnew43how completely this was documenteddepth20/40specificity15/30actionability8/3043 / 100
Syncs users and groups directly from Google Workspace into Clerk, with support for role mapping and custom attributes.
Device Trust for new-device sign-insnew38how completely this was documenteddepth20/40specificity10/30actionability8/3038 / 100
A new Device Trust capability automatically requires a second factor when a user signs in with a password from a new device and has not enabled MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone..
— Explains behaviour but no config surface or flag namedproduct docs
0300
Community-maintained Flutter integration docsnew23how completely this was documenteddepth10/40specificity8/30actionability5/3023 / 100
Adds community-maintained Flutter integration support, with dedicated documentation for integrating Clerk into Flutter applications.
— Only states docs exist, no specific API or steps givenproduct docs
SailPoint is an identity governance and access management platform that automates user access provisioning, certification, and compliance across enterprise systems.
SailPoint introduced Agentic Fabric, a full AI agent and non-human identitynon-human identityA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. governance layer for Identity Security Cloud spanning endpoint and browser sensors, SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents./EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. and cloud source connections, a unified Non-Human Identity Registry, sanctioned/unsanctioned app classification, identity graphs, audit reporting, and configurable aggregation, alongside new Dark Mode support across Agentic Fabric and select Identity Security Cloud pages.
└──▷ WHAT SHIPPED ·
13 FEATURES12 OF 13 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Endpoint agent sensor for AI discoverynew70how completely this was documenteddepth25/40specificity30/30actionability15/3070 / 100
A background endpoint agent, managed by navigating to Admin > Global > Agent Settings > Sensors and selecting the Endpoint Agent tab, discovers AI agent software installed on managed laptops and desktops.
After activating Agentic Fabric, manage the endpoint agent sensor that discovers AI software running on corporate endpoints.
📍In Identity Security Cloud, go to Admin › Global › Agent Settings › Sensors, then select the Endpoint Agent tab to view and update endpoint agent configuration.
— Exact admin path given; describes purpose but not internals.product docs
0202
SIEM and EDR connections for agent monitoringnew68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Navigating to Admin > Global > Agent Settings and selecting SIEM and EDR Connections lets admins connect EDR or SIEM platforms so Agentic Fabric can discover and monitor AI agents.
Connect an EDR or SIEM platform post-activation so Agentic Fabric can automatically find available data sources for AI agent monitoring.
📍In Identity Security Cloud, go to Admin › Global › Agent Settings, then select SIEM and EDR Connections from the left panel to add or update your EDR/SIEM integration.
— Exact nav path and example steps, but UI-only action.product docs
0303
Identity provider correlation for AI agent ownershipnew68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Under Admin > Security Settings > Service Provider, admins manage identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. (Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. or Okta) post-activation to correlate human identities to the AI agents they own.
— Named path and providers, but no example walkthrough.product docs
0404
Business Apps sanction status groupingnew68how completely this was documenteddepth28/40specificity25/30actionability15/3068 / 100
A new Business Apps grouping lets administrators declare a sanction status — sanctioned, unsanctioned, or unknown — for logical applications and agents, with matching agents automatically inheriting that classification.
Classify which AI tools and agents are permitted or prohibited so that matching agents automatically inherit the sanctioned/unsanctioned status.
📍In Identity Security Cloud, go to Agentic Fabric › Business Apps, select a business app, and set its sanction status to Sanctioned, Unsanctioned, or Unknown.
— Exact statuses and example steps, though UI-only.product docs
0505
Cloud platform sources for non-human identity aggregationnew65how completely this was documenteddepth22/40specificity28/30actionability15/3065 / 100
Via Admin > Connections > Sources, admins connect cloud platforms (AWS, Azure, and other AI platforms) as sources for aggregating non-human identitiesnon-human identitiesA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls..
— Named path and platforms, no example given.product docs
0606
Browser extension sensor for GenAI governancenew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
A browser extension sensor, managed via Admin > Global > Agent Settings > Sensors under the Browser Extension tab, governs GenAI usage across managed and unmanaged SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. environments.
— Named admin path but no usage example provided.product docs
thinner coverage below
0707
Configurable per-dataset aggregation for non-human identitiesnew57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
A datasets and resources model lets SailPoint sources aggregate non-human identities, AI agents, MCPMCPModel 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. servers, credentials, and IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role objects on a configurable per-dataset aggregation schedule.
— Names object types and schedule concept, no exact config key.product docs
0808
Non-Human Identity Trends widgetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
A new widget on the MySailPoint home page shows total non-human identity counts over a selected time window, with day-level detail available on hover.
— Describes behaviour but no interaction steps.product docs
0909
Non-Human Identity Registrynew50how completely this was documenteddepth20/40specificity22/30actionability8/3050 / 100
A new unified Non-Human Identity Registry centralizes discovery and management of agents, applications, accounts, MCP servers, credentials, and endpoints.
— Names object types covered but no navigation or config given.product docs
1010
Audit and compliance reporting for AI agentsnew45how completely this was documenteddepth22/40specificity18/30actionability5/3045 / 100
Audit and compliance reporting produces auditor-ready records covering agent inventory, ownership, action audit trails, and compliance evidence packaging.
— Lists record types but no access path or format.product docs
1100
Dark Mode across Agentic Fabric and ISCnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Dark Mode support is added across SailPoint Agentic Fabric and a select number of Identity Security Cloud pages, and is user-configurable per account. Custom branding colors are not applied in Dark Mode and continue to appear only in Light Mode.
Immuta is a data governance platform that controls access to sensitive data and ensures compliance through automated policies and masking.
Immuta shipped a native Trino/Starburst integration with direct policy enforcement on Trino objects, alongside a Connections UI overhaul adding health-state indicators, per-object policy sync controls, tag inheritance, and Redshift automated data discovery — plus several breaking changes affecting Databricks query audit and Snowflake policy roles.
└──▷ WHAT SHIPPED ·
12 FEATURES2 OF 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Native Trino/Starburst integrationnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
A new Trino integration lets teams register a Trino connection so Immuta can administer access controls and enforce Immuta policies directly on objects and end-user access within Trino. It includes customizable Trino plugin properties to tailor the plugin configuration, write access mapping to customize how read/write access policies are enforced for Starburst (Trino), rotation of the system API key for the integration, and supported authentication methods and audit features for compliance.
— Describes mechanism and config surfaces but no exact commandsproduct docs
0200
Automated data discovery for Redshift viewless integrationnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Automated sensitive data discovery now supports Immuta's Amazon Redshift viewless integration, covering regex, dictionary, and column-name-regex identifier types.
Per-object policy sync togglenew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
A new per-object policy sync setting in Connections controls whether Immuta pushes policy down to the data platform for a given data object, showing a Custom label when a child object's setting differs from its parent's.
New Immuta-managed built-in groupsnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Three new Immuta-managed built-in groups — All Agents, All Users, and All Identities — are now available for use in subscription policies and data policies.
Integration settings moved into Connections UIimproved45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Integration settings for Databricks Unity Catalog and Snowflake connections now live directly within the Connections UI rather than in a separate settings area.
Snowflake integration error banners removedbreaking40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Integration error banners for Snowflake integration validation failures will no longer be displayed; errors will instead appear in the new Connections experience.
Starting August 26, 2026, Databricks will mask query_text in the query_history system table by default; Immuta query audit will no longer contain query text and all query audit events will show as Indeterminant unless the Immuta service principal is added to the databricks_pii_access group in Databricks.
!
Immuta policy role names used to grant users access to Snowflake data sources will be renamed and recreated as part of the Snowflake integration architecture update rolling out from July 23, 2026 (user role names remain unchanged).
!
Integration error banners for Snowflake integration validation failures will no longer be displayed; errors will instead appear in the new Connections experience.
OpenVPN v2.7.6 simplifies default configuration by making tun the implicit device and enabling TCP_NODELAY by default, while capping keepalive timers at 24 hours.
└──▷ WHAT SHIPPED ·
3 FEATURES2 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
TCP_NODELAY enabled by defaultbreaking78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
The TCP_NODELAY socket flag is now always enabled on the local socket, whereas previously it required --tcp-nodelay. In server mode, --tcp-nodelay now specifically pushes socket-flags TCP_NODELAY to clients that may not have this default.
— Explains mechanism and server-side push behavior with flag names.v2.7.6
0200
Default device changed to tunimproved70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Omitting --dev from an OpenVPN config now defaults to --dev tun, removing a previously required boilerplate option for the common tun case.
— Names exact flag and default change, no example.v2.7.6
0302
24-hour cap on ping and keepalive intervalsbreaking70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
The --ping and --keepalive options now reject values exceeding 86400 seconds (24 hours); configs with larger values will need to be updated.
— Gives exact limit and required migration action.v2.7.6
└──▷ BREAKING ON UPGRADE
!
The --ping and --keepalive options now reject values exceeding 86400 seconds (24 hours); configs with larger values will need to be updated.
!
TCP_NODELAY is now enabled by default on all sockets; previously it was opt-in via --tcp-nodelay.
Zscaler is a cloud-based security platform providing zero-trust network access, threat prevention, and data protection for organizations.
Zscaler shipped AI Guard integration with Anthropic's Claude inference hooks, extending Zero Trust DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. policy enforcement directly into the Claude model layer.
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
AI Guard integration with Claude inference hooksnew62how completely this was documenteddepth30/40specificity20/30actionability12/3062 / 100
Zscaler AI Guard integrates with Anthropic Claude inference hooks to enforce Zero Trust data-loss-prevention policy natively at the Claude model layer, evaluating full conversation context in real time rather than individual messages. Existing Zscaler platform policies extend to Claude Enterprise touchpoints with no additional governance stack required, and existing Zscaler customers can activate the feature using their current policy configuration.
— Names product and integration point but no config key or endpoint.2026-08-05-1bd71b85
ScoutDNS is a DNS reconnaissance and security tool that maps domain infrastructure, identifies misconfigurations, and monitors DNS records for vulnerabilities.
ScoutDNS shipped a ground-up console redesign this cycle, adding explicit match/subtree controls and comments for allow/block list rules, an auto-generated Zero Trust TLDTLDThe rightmost label in a domain name (e.g., .com, .gov, .uk), maintained by IANA's root zone. Cyber tools filter or pivot on TLDs to scope scans, flag suspicious registrations, or classify traffic by geography or type. allowlist, per-policy Secure Scores, a cross-tenant MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. dashboard, and dark mode.
└──▷ WHAT SHIPPED ·
9 FEATURES0 OF 9 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Match/subtree option on allow/block list rulesnew65how completely this was documenteddepth25/40specificity22/30actionability18/3065 / 100
Every custom allow/block list rule now carries a match or subtree option that makes explicit whether the rule covers a single hostname or a domain and all its subdomains; a single wildcard entry using subtree now covers both the domain and its subdomains, removing the need for two separate entries.
Deployments subtab on Policies pagenew57how completely this was documenteddepth22/40specificity20/30actionability15/3057 / 100
A new Deployments subtab on the Policies page shows every policy assignment across sites, profiles, and personas in one account-wide view, with inline editing.
RegScale is a compliance and regulatory management platform that automates governance, risk, and compliance (GRC) workflows for organizations.
RegScale CLI 6.38.0 adds eMASSeMASSA U.S. DoD web application that manages the Risk Management Framework process, tracking system authorizations, controls, and POA&Ms so cyber tools can automate compliance reporting into a single authoritative record. CAC authentication support for custom CA bundles (e.g. DoD PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets.) via config, env var, and CLI flag.
└──▷ TRY IT
Register an eMASS API connection trusting a DoD PKI CA bundle when running in a CI/CD pipeline where env vars are preferred over config files.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline this window focused on model catalog updates and a major overhaul of reasoning-effort handling, standardizing it across all AI SDK providers including Ollama, alongside a friendlier UX for retired free-model promotions.
└──▷ WHAT SHIPPED ·
3 FEATURES1 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Unified reasoning effort control across AI SDK providersbreaking65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Reasoning effort settings (effort levels and enable/disable toggles) now map to a shared path across all AI SDK providers, including Ollama, instead of going through per-provider thinking overrides; disabling reasoning is respected everywhere. Per-provider thinking overrides are replaced by the AI SDK's native reasoning setting, so existing configurations relying on those overrides will need to be updated.
Dedicated notice for retired free model promotionsnew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
When a retired free model is requested, Cline shows a dedicated notice with a button to pick another model, instead of a generic error with only a Retry prompt.
— Describes behavior change but no UI path or config named.v4.1.5
└──▷ BREAKING ON UPGRADE
!
Per-provider thinking overrides are replaced by the AI SDK's native reasoning setting; existing configurations relying on those overrides will need to be updated.
Lightweight coding agent that runs in your terminal
OpenAI Codex CLI's rust v0.147.0 alpha series added per-session code-mode execution limits, a --concurrent-requests flag for the exec-server, managed authentication enforcement via requirements.toml, Amazon Bedrock hosted web search with cached fallback, and new thread-section and MCPMCPModel 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. APIs, alongside a long tail of sandboxingsandboxingRunning code inside a restricted environment that limits what it can access or change. The isolation reduces the impact of mistakes or untrusted code, depending on the sandbox's controls., telemetry, and TUITUIA text-based user interface that runs inside a terminal, using characters and ANSI escape codes to render menus, panes, and widgets without a graphical desktop, letting cyber tools ship rich interactivity with no GUI dependency. reliability improvements.
└──▷ WHAT SHIPPED ·
0 FEATURES34 FEATURES0 OF 34 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
`--concurrent-requests` flag for exec-servernew88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
Adds --concurrent-requests flag (alias concurrent-requests, default 1) to the exec-server subcommand to enable opt-in concurrent request dispatch across connections, e.g. codex exec-server --concurrent-requests 4 --listen ws://127.0.0.1:9000.
Run the exec-server with concurrent request processing enabled to handle multiple client requests in parallel.
Managed auth enforcement via `requirements.toml`new83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
Enforces managed authentication requirements locally via a requirements.toml allowlist for login methods and ChatGPT workspaces, combining managed and existing workspace restrictions by intersection and failing closed when no usable login method remains.
`create_session_with_limits` for per-session execution capsnew78how completely this was documenteddepth32/40specificity28/30actionability18/3078 / 100
Adds create_session_with_limits and session-scoped cell execution limits via CodeModeSessionCellExecutionLimits, clamping execute and wait yield times to max_yield_time_ms without terminating the running cell.
`thread/section/move` API and section orderingnew73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
Adds a thread/section/move API endpoint and section_position sorting to thread/list, allowing threads to be reorganized into sections and listed in section order.
Guardian reviews switch to `gpt-5.6-luna` for API-key authimproved72how completely this was documenteddepth32/40specificity28/30actionability12/3072 / 100
Switches Guardian approval reviews authenticated with an API key to use gpt-5.6-luna, while retaining codex-auto-review for ChatGPT authentication; falls back to the bundled Guardian policy when the selected model has no catalog-provided review policy.
`image_resize_notice` developer message featurenew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds the disabled-by-default image_resize_notice feature: when enabled, it appends a developer message after resized images in user messages or tool outputs, reporting each image's original and prepared dimensions.
Amazon Bedrock hosted web search with cached fallbacknew64how completely this was documenteddepth30/40specificity22/30actionability12/3064 / 100
Enables hosted web search for Amazon Bedrock, automatically resolving unsupported live and indexed modes to cached search, or disabling the tool when cached search is prohibited by managed requirements.
500 ms bound on TUI telemetry shutdownimproved63how completely this was documenteddepth28/40specificity25/30actionability10/3063 / 100
Bounds interactive TUI telemetry shutdown to a 500 ms budget via OtelProvider::shutdown_with_timeout, preventing a stalled OTLPOTLPOpenTelemetry Protocol, a standard way to send traces, metrics and logs between applications, collectors and monitoring systems. It lets telemetry move across compatible tools. exporter from blocking indefinitely on exit.
Case-insensitive Windows path URI comparisonsimproved60how completely this was documenteddepth28/40specificity22/30actionability10/3060 / 100
Makes Windows path URI comparisons ASCII-case-insensitive for drive and UNC paths while preserving case-sensitive POSIXPOSIXA family of standards for operating-system interfaces, including process, file and shell behavior. Software that uses these interfaces is easier to move between compatible systems. behavior, including starts_with and relative_path_from operations.
`McpBinding` caching per MCP runtimeimproved58how completely this was documenteddepth28/40specificity22/30actionability8/3058 / 100
Caches McpBinding per published MCP runtime once the tool catalog revision is stable, reusing it across sampling steps and rebuilding only after a runtime publish or catalog change.
Symlinked skill discovery path preservationimproved53how completely this was documenteddepth25/40specificity18/30actionability10/3053 / 100
Preserves discovery paths for symlinked skills in the skill catalog, allowing either the discovery path or canonical path to be used for structured selections and linked skill mentions.
Secret redaction in app-server command execution displayimproved46how completely this was documenteddepth20/40specificity18/30actionability8/3046 / 100
Redacts secrets, including bearer tokensbearer tokensA 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., from app-server command execution items in display output.
MCP credential isolation by environmentimproved41how completely this was documenteddepth18/40specificity15/30actionability8/3041 / 100
Hosted MCP credentials are now restricted to local environments, and MCP OAuthMCP OAuthAn authentication layer for the Model Context Protocol that lets MCP clients obtain delegated access tokens so cyber tools can call MCP servers on a user's behalf without handling raw credentials. credentials are isolated by environment.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Claude Code v2.1.223 adds owner-level wildcard controls for marketplace allow/block lists, a /teleport command for moving cloud sessions to a local machine, and an upgraded /code-review with effort levels and PR targeting, alongside new env vars for controlling context-window behavior.
└──▷ WHAT SHIPPED ·
6 FEATURES0 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
/code-review effort levels and PR targetingimproved95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Makes /review an alias of /code-review; /code-review now accepts an effort level and PR number via /code-review <level> <pr#>, with /code-review ultra triggering a deep cloud review (e.g. /code-review ultra 4321). It also remembers the last effort level used when invoked without one, so repeat reviews don't require retyping the level.
Run a deep review of a pull request straight from the terminal using the new effort-level syntax.
$ /code-review ultra 4321
— Exact command syntax and runnable example givenv2.1.223
0200
Owner wildcard marketplace controlsnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds "owner/*" wildcard entries to strictKnownMarketplaces and blockedMarketplaces managed settings, allowing or blocking all marketplace repos under a GitHub org in a single entry, e.g. {"blockedMarketplaces": ["acme-corp/*"]}.
Block all marketplace repos from a specific GitHub org in managed settings with a single wildcard entry instead of listing each repo.
json
{
"blockedMarketplaces": ["acme-corp/*"]
}
— Exact config keys and runnable example givenv2.1.223
0300
/teleport cloud-to-local session handoffnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds a claude --teleport <session id> flag and a /teleport hint shown in cloud sessions, letting a user continue a cloud session locally.
Pick up a cloud session on your local machine when you need to switch environments mid-task.
Expanded 1M context auto-compaction capimproved70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Expands CLAUDE_CODE_DISABLE_1M_CONTEXT to cap every Claude model with a native 1M context windowcontext windowThe maximum amount of text, counted in tokens, a model can take in and produce in one request. Everything the model knows about the task has to fit inside it. to 200K via auto-compaction, rather than only a fixed model list, and adds a startup warning when auto-compaction isn't holding the session to 200K.
— Named env var and behavior, no usage examplev2.1.223
0500
Opt-out of unknown model context window enforcementnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1 env var to opt out of the new behavior that keeps sessions on unrecognized model IDs within the assumed context window.
Warning for restricted subagent model fallbacknew45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
Adds a warning when a workflow agent, forked skill, slash command, or resumed background agent's requested subagent model is restricted and the parent model runs instead.
— Describes behavior only, no named surface or examplev2.1.223
OpenCode adds Poolside as a supported provider with self-hosted deployment configuration, and streamlines xAI (Grok) authentication with a device-code OAuth flow alongside API key access.
└──▷ WHAT SHIPPED ·
2 FEATURES0 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Poolside provider support with self-hosted deployment confignew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
OpenCode adds Poolside as a supported provider via its OpenAI-compatible API, with API keys configured at platform.poolside.ai or stored locally at ~/.secrets/poolside-key for self-hosted deployments. Self-hosted Poolside instances are set up as a custom OpenAI-compatible provider with a custom provider ID and base URL (e.g. https://poolside.example.com/openai/v1), discovering model IDs via the /openai/v1/models endpoint, and support the reasoning_content field plus interleaved reasoning mode for thinking-capable models.
Configure a self-hosted Poolside deployment as a custom provider, storing credentials outside the config file.
— Named endpoint, file path and full JSON config example included.product docs
0200
xAI (Grok) authentication via SuperGrok OAuth and API keyimproved60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
OpenCode adds two xAI authentication paths: a SuperGrok subscription via device-code OAuth, where OpenCode opens xAI's verification link with the user code pre-populated and automatically polls the token endpoint, or a pay-as-you-go API key obtained from the xAI console. In v1.18.14 this login flow was simplified to a single device-code flow to better support headless and remote environments.
— Describes mechanism and simplification but gives no exact command.v1.18.14
OpenHands v1.10.0 adds activity log export, a featured automations dashboard, manifest-driven automation sub-pages, faceted skills filtering, and switches Canvas's default model to GLM 5.2.
└──▷ WHAT SHIPPED ·
5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Faceted skills filteringnew40how completely this was documenteddepth15/40specificity10/30actionability15/3040 / 100
Adds faceted rail filtering to the Skills page for faster skill discovery.
— Names UI location (Skills page) but no filter facets listedv1.10.0
0200
Manifest-driven automation sub-pagesnew35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds manifest-driven sub-pages to the automation interface, enabling structured automation workflows.
— Mentions manifest-driven mechanism but no schema or file pathv1.10.0
0300
GLM 5.2 default model for Canvasimproved35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Sets GLM 5.2 as the default model for Canvas.
— Names specific model and feature but no config or override infov1.10.0
0400
Featured automations landing dashboardnew30how completely this was documenteddepth15/40specificity5/30actionability10/3030 / 100
Ships a featured automations landing dashboard for discovering and launching automations.
— Describes purpose but no navigation path or detailsv1.10.0
0500
Activity log exportnew25how completely this was documenteddepth10/40specificity5/30actionability10/3025 / 100
Adds activity log export capability to the interface.
— Names the capability but no format or location givenv1.10.0
Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
CrewAI 1.15.12 consolidates project scaffolding into a single command, adds a URL-reading tool for agent workflows, and attaches app metadata to platform action tools.
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Unified `crewai create <resource>` scaffoldingimproved70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
Replaces separate scaffold commands with a single unified crewai create <resource> command for generating new CrewAI resources such as crews or flows.
Scaffold a new CrewAI resource (crew, flow, etc.) using the unified create command.
Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.
Ollama v0.32.6 brings OpenAI-compliant streaming usage reporting and automatic speculative decodingspeculative decodingSpeeding up generation by letting a small draft model guess several tokens ahead and having the large model check them all at once. Output is unchanged; accepted guesses save time. for Qwen3.5 on Apple GPUsGPUsA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference., while removing the experimental image generation feature.
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
stream_options.include_usage in chat completions APIimproved90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds stream_options.include_usage support in /v1/chat/completions so usage is returned in a separate trailing chunk, matching OpenAI's streaming wire format — role now appears only on the first chunk and finish_reason on its own chunk.
Stream a chat completion and receive token usage in a separate trailing chunk, matching OpenAI's wire format.
$ curl http://localhost:11434/v1/chat/completions -d '{"model": "gemma4", "stream": true, "stream_options": {"include_usage": true}, "messages": [{"role": "user", "content": "Why is the sky blue?"}]}'
— Named endpoint, field, and runnable curl example providedv0.32.6
thinner coverage below
0200
Automatic MTP speculative decoding for Qwen3.5 on Apple GPUsimproved50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
Qwen3.5 inference on Apple GPUs is faster because the MLXMLXApple's machine-learning framework for Apple silicon, which uses the unified memory shared by CPU and GPU to run and fine-tune models on a Mac. engine now automatically uses the model's MTP head for speculative decoding.
— Explains mechanism but no config or flag to invoke itv0.32.6
0300
Experimental image generation removedbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Experimental image generation has been removed in v0.32.6; users must continue using v0.32.5 for image generation support.
— Clear removal noted with version to revert tov0.32.6
└──▷ BREAKING ON UPGRADE
!
Experimental image generation is no longer available in v0.32.6; the feature has been removed and requires staying on v0.32.5.
Open-Source Evaluation & Testing library for LLM Agents
Giskard v1.0.1b6 extends its vulnerability scanner with third-party integration, tightens judge check reliability, and exposes internal scan generators publicly.
└──▷ WHAT SHIPPED ·
0 FEATURES3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Public export of default registry generatorsimproved60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Default registry generators are now exposed on the public API via chore(scan): export default registry generators on the public API, making it easier to inspect and reuse built-in ScenarioGenerator instances.
— Names API export and ScenarioGenerator class but no usage example.giskard-core/v1.0.1b6
thinner coverage below
0200
Third-party scan integration in vulnerability_scannew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
vulnerability_scan now integrates third-party scan support via the new feat(scan): integrate third party scan capability, extending the scanner beyond its built-in generators.
— Names the function and capability but not the third-party interface.giskard-core/v1.0.1b6
0300
Non-blank judge reason enforcementimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
LLMLLMA 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.-as-judge checks now enforce non-blank judge reasons — evaluations that return an empty reason string fail explicitly instead of silently passing.
ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.
ToolHive's v0.42.0 release introduces a full CLI and REST APIREST APIA 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. for AI-tool plugin management via thv ai-plugin, complete with a registry catalog and Sigstore signature verification, alongside concurrent stdio-server sharing across MCPMCPModel 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. clients — and ships several breaking changes touching CRDCRDA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. status fields, Cedar authorization ordering, panic logging, and internal telemetry APIs.
└──▷ WHAT SHIPPED ·
8 FEATURES0 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Removed status.referencingWorkloads fields from config CRDsbreaking90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
status.referencingWorkloads and status.referenceCount fields (and the References printer column) are removed from all six config CRDsCRDsA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. (MCPOIDCConfig, MCPAuthzConfig, MCPExternalAuthConfig, MCPToolConfig, MCPWebhookConfig, MCPTelemetryConfig); replace any automation that reads them with workload field queries.
— Names exact CRDs, fields, and required migration pathv0.42.0
0200
Cedar authorization evaluated post-mutationbreaking90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Cedar authorization policy is now evaluated against the post-mutation MCP request — if you run a mutating webhook (--webhook-config with a mutating: entry, or MCPWebhookConfig.spec.mutating) alongside Cedar authz, policy decisions and audit records (type, target.name) can change on upgrade; re-audit policies against the post-mutation shape before upgrading.
— Details exact flags, audit fields, and required re-audit actionv0.42.0
thinner coverage below
0300
thv ai-plugin CLI and REST APInew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds thv ai-plugin subcommand with a full CLI and REST API for end-to-end AI-tool plugin management.
— Names command and API but no endpoints or flags listedv0.42.0
0400
Removed pkg/telemetry/providers and optimizerdec constantsbreaking55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
pkg/telemetry/providers was deleted and two long-published optimizerdec constants were removed from the Go API, breaking any out-of-tree importers that reference them.
— Names removed package and constants but no migration guidancev0.42.0
0500
Sigstore signature verification for pluginsnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds Sigstore signature verification for skills/plugins at install, sync, and upgrade time.
— Names trigger points but no config flag or commandv0.42.0
0600
Recovered HTTP panics no longer loggedbreaking50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Recovered HTTP panics no longer emit a slog.Error log line or stack trace — setups relying on log-based alerts or support bundles to diagnose recovered panics will silently lose that diagnostic output (a patch fix is expected).
— Explains impact and notes upcoming fix, no interim action givenv0.42.0
0700
ai-plugin registry catalognew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds a registry catalog to thv ai-plugin for discovering and deploying plugins from a curated index.
— Describes purpose but no catalog commands or fields givenv0.42.0
0800
Concurrent stdio server sharing across MCP clientsimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Enables multiple MCP clients to share a single stdio server concurrently.
— Brief statement with no mechanism or configuration detailv0.42.0
└──▷ BREAKING ON UPGRADE
!
status.referencingWorkloads and status.referenceCount fields (and the References printer column) are removed from all six config CRDs (MCPOIDCConfig, MCPAuthzConfig, MCPExternalAuthConfig, MCPToolConfig, MCPWebhookConfig, MCPTelemetryConfig); replace any automation that reads them with workload field queries.
!
Cedar authorization policy is now evaluated against the post-mutation MCP request — if you run a mutating webhook (--webhook-config with a mutating: entry, or MCPWebhookConfig.spec.mutating) alongside Cedar authz, policy decisions and audit records (type, target.name) can change on upgrade; re-audit policies against the post-mutation shape before upgrading.
!
Recovered HTTP panics no longer emit a slog.Error log line or stack trace — setups relying on log-based alerts or support bundles to diagnose recovered panics will silently lose that diagnostic output (a patch fix is expected).
!
pkg/telemetry/providers was deleted and two long-published optimizerdec constants were removed from the Go API, breaking any out-of-tree importers that reference them.
Obsidian is a personal knowledge management app that lets users create, link, and organize markdown notes locally with powerful search and graph visualization.
Obsidian's early-access desktop and mobile builds add a new plugin API hook, richer startup diagnostics, and several mobile tab and UI refinements including swipe-to-close tabs and proportional checkbox scaling.
└──▷ WHAT SHIPPED ·
0 FEATURES5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
SettingDefinitionBase#disabled API additionnew45how completely this was documenteddepth10/40specificity20/30actionability15/3045 / 100
The desktop API gains SettingDefinitionBase#disabled, letting plugin developers mark setting definitions as disabled.