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.
Bugcrowd Researcher Platform connects security researchers with organizations to identify and report vulnerabilities through crowdsourced bug bounty programs.
Bugcrowd Researcher Platform now supports researcher participation in Bugcrowd Gov (US) engagements under 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. compliance.
└──▷ 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
FedRAMP support for Bugcrowd Gov engagementsnew35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
The platform now supports researcher participation in Bugcrowd Gov (US) engagements under FedRAMP compliance, letting researchers hack on government programs subject to that standard.
Bugcrowd is a crowdsourced security testing platform connecting organizations with ethical hackers to identify and report vulnerabilities.
Bugcrowd shipped 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. support for compliance-sensitive customers alongside two new reporting surfaces: an on-demand Vulnerability Detections dashboard and a DNS Records CSV export for auditors and leadership.
└──▷ 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.
0100
DNS Records CSV export reportnew75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
A new DNS records (csv) report type under Organization > Reports exports a point-in-time inventory of discovered assets — names, types, and discovery source — filterable by creation date range. Generated reports are emailed when ready and remain accessible to all Owner roles from the Reports page as timestamped snapshots.
Generate a DNS records CSV for a quarter to hand auditors a defensible record of attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. growth without waiting on engineering.
📍Go to Organization › Reports, click Generate report, select DNS records (csv) from the dropdown, provide a Report Title and Date Range, then click Generate report. Download the artifact from the Reports page once the email notification arrives.
— Names exact report type, fields, and full generation stepsproduct docs
0200
Vulnerability Detections dashboard in AI Analyticsnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
A new Vulnerability Detections tab under Organization > AI Analytics lets Owners filter by date range, vulnerability priority, asset group, and asset owner to scope posture views to a specific business unit or asset owner before a leadership review.
Scope the Vulnerability Detections dashboard to a specific business unit before a leadership review.
📍Go to Organization › AI Analytics, click the Vulnerability Detections tab, then apply filters for date range, vulnerability priority, asset group, or asset owner to focus on the relevant business unit.
— Names exact tab and filters with navigation steps, but no mechanism detailproduct docs
thinner coverage below
0301
FedRAMP support for compliance environmentsnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Bugcrowd added FedRAMP support, enabling government and compliance-sensitive organizations to use the platform within FedRAMP-authorized environments.
A pentesting tool for enumeration/download/graphical analysis of OCI content. Includes an OpenGraph generator for Bloodhound-style analysis.
OCInferno gains exploit modules, 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. stripping, delegation auth, container image tokens, IDD self-service, and new enumeration flags.
└──▷ TRY IT
Enumerate OCI identity resources and save discovered domain URLs to the database for later use in IDD attacks.
$ ocinferno enum_identity --save-domains
Scope an enum_all run to specific regions to avoid timeouts on unsupported OCI endpoints.
Acunetix 360 is a cloud-based web application security scanning platform that identifies vulnerabilities through automated dynamic and static analysis.
Acunetix 360 adds partial-update support to its scan profile and policy APIs, extends scan data retention to two years, and upgrades core services to .NET 10.
└──▷ 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
PATCH support for scan profile and policy APIsimproved70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Adds PATCH semantics to scan profile and policy API endpoints, allowing partial updates that preserve existing values without resubmitting the full configuration object.
C/Side is a cloud-based IDE for Dynamics 365 Business Central development, enabling creation and modification of extensions and customizations.
c/side introduced CSPCSPContent Security Policy: a browser security mechanism, standardized by the W3C, that lets a web server declare which sources of scripts, styles, and other resources a page may load, blocking injection attacks. Builder, a tool that turns observed script hosts into a deployable Content-Security-Policy with a review and report-only rollout workflow.
└──▷ 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
CSP Builder for policy generation and rolloutnew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
CSP Builder generates a suggested Content-Security-Policy from hosts c/side has already observed on your site, covering seven directives: script-src, connect-src, img-src, style-src, frame-src, font-src, and media-src. You can review the suggested policy, toggle off unexpected hosts, and add hosts not yet observed before deploying, and the workflow supports deploying a report-only header first, monitoring violations in the dashboard, then switching to enforce mode once the policy is clean.
— Names directives and workflow steps but no exact header/config syntax.Introducing CSP Builder
trufflehog discovers, classifies, and validates leaked credentials
TruffleHog's headline additions this window are Slack scanning for Enterprise Edition, AWS credential analysis via aws analyze, and a cross-source Activity Log with a read API; the open-source CLI gains SARIFSARIFStatic Analysis Results Interchange Format, a standard for sharing code-analysis findings, including locations and rule details. It lets scanners report results to a common review interface. output (--sarif), a large set of custom regex detector tuning options, S3 custom endpoints, and eight new detectors, while Enterprise also picks up source archiving, SharePoint historical scanning, Google Drive domain-wide delegation, and 16 more detectors.
└──▷ WHAT SHIPPED ·
22 FEATURES3 OF 22 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
Custom regex detector configuration optionsimproved100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
Custom regex detectors (beta), wired in via the detectors field of the TruffleHog config YAML with keywords, name, regex, and verify (with endpoint, headers, unsafe) sub-keys, gain a set of tuning parameters: successranges under verify to specify HTTP status codes or inclusive ranges (e.g. '200-202') that mark a secret as live/verified; rotatedranges under verify to specify codes or ranges (e.g. '401', '403') that mark a secret as definitively rotated/unverified; entropy to filter detected strings by randomness score and cut false positives; exclude regexes capture to strip sub-portions of a detected secret from the reported result; exclude regexes match to suppress entire matches from being reported; exclude words to ignore strings containing specified words; and primary regex name to designate which named regex pattern determines the reported line number when multiple regexes are defined under the regex field, with capture groups for extracting specific secret segments and a requirement that all named regexes match for a detection to succeed.
Distinguish live secrets from rotated ones during verification so your triage queue only surfaces actionable findings.
— Names every config key with a runnable example YAML config.product docs
0201
Activity Log for scan events (Enterprise)new90how completely this was documenteddepth40/40specificity30/30actionability20/3090 / 100
New Activity Log gives a top-level view of scan lifecycle events — scan started, scan completed, scan failed, scan scheduled, and scan anomaly detected — across every source, filterable by date range, event, status, source, and actor, with filters stored in the page URL for shareable views; events are append-only with 90-day retention. Scan events carry one of six statuses — success, partial, failure, in progress, scheduled, or warning — shown as color chips, and anomaly-detection heuristics flag completed scans that scanned no data or finished suspiciously fast. Each row opens a detail drawer with full message text and a direct, shareable URL. A read API is available so scan failures can be routed into external monitoring and alerting tools, with API documentation shipping alongside it; source IDs are exposed via the API only. Archiving a source preserves its Activity Log history, while deleting a source removes its events along with its findings.
— Full statuses, filters, retention and API named; exact endpoint path omitted.product docs
0300
SARIF output for scan resultsnew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds --sarif flag for SARIF-format output compatible with GitHub code scanning's github/codeql-action/upload-sarif action, tracking findings as new/fixed across scans.
Upload TruffleHog results to GitHub code scanning in a CI workflow — SARIF lets GitHub inline findings on PR diffs and deduplicate across runs.
Source archiving in Enterprisenew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
A source can be archived to stop scanning while retaining all findings with triage history intact, accessible from the three-dot menu on a source row in Integrations; show archived reveals archived sources, and archiving requires admin or editor role. Archived sources are now filtered server-side in the sources list, keeping the integration list responsive for large deployments.
— Exact UI navigation, filter and role requirement given.product docs
0502
Slack scanning in Enterprise Editionnew75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
TruffleHog Enterprise adds Slack as a listed app in the Slack Marketplace, scanning messages, threads, and attached files for credentials and verifying each finding as live or not. Continuous scanning covers public channels, private channels the app is invited to, DMs, and group DMs, with edited messages rescanned and the app auto-joining new public channels. Historical scanning covers messages, threads, and attachments including archives, base64-encoded data, binaries, and Microsoft Office documents, with include/exclude lists to scope channel coverage and resumable scans after interruption.
— Full mechanism and scope described, but no exact setup steps given.product docs
0603
AWS credential analysis (`aws analyze`)new75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds aws analyze for customers on the Analyze SKU — resolves effective permissions, discovers 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 chaining paths, and warns on IAM conditions and policy variables.
— Names the exact command and SKU with concrete analysis behaviour.product docs
0700
New detectors and Cloudflare format support in Enterprise scanningnew60how completely this was documenteddepth20/40specificity30/30actionability10/3060 / 100
Adds 16 new detectors to Enterprise scanning: Braintrust, Cloudflare API Token, Cloudflare Global API Key, Cloudinary, Duffel, Duo, GitLab OAuth, HashiCorp Vault Token, HashiCorp Vault Batch Token, New Relic Insights Insert Key, Octopus Deploy, pganalyze Read Key, Pinecone, Red Hat Pyxis, Shippo, and SonarQube Cloud — the SonarQube Cloud scoped organization token, Duo API secret key, and Cloudflare detectors are new in both Enterprise and open source. Also adds recognition of the new 2026 prefixed Cloudflare credential formats for both the Cloudflare API Token and Global API Key detectors in Enterprise and open source.
— Names every detector and format but gives no config or flag to invoke.product docs
0800
Verification freezing for archived sourcesnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Scanning stops immediately when a source is archived, including in-flight scans. Verification only freezes for a finding once every source behind it is archived; frozen findings retain their last verification status and are excluded from MTTR calculations.
— Explains exact freeze condition and MTTR effect.product docs
thinner coverage below
0900
Encrypted private keys surfaced as findingsimproved55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Encrypted (passphrase-protected) private keys are now reported as findings even when the passphrase cannot be recovered, surfaced as unverified findings carrying encrypted:true metadata instead of being silently dropped.
— Names the metadata field but not a flag to control it.v3.97.0
1000
Domain-wide delegation for Google Drive integrationnew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
The add integration wizard for Google Drive now supports domain-wide delegation, enabling scanning with the access of all domain users in a single integration, for both hosted and self-hosted scanners.
— Names the exact wizard and scanner types but no setup steps.product docs
1100
Per-clone subdirectories for `--clone-path`improved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Each clone under --clone-path now gets its own subdirectory, preventing collisions when scanning multiple repositories concurrently.
— Names the flag and the before/after behaviour.v3.97.0
1200
New detectors in v3.97.0new45how completely this was documenteddepth15/40specificity25/30actionability5/3045 / 100
Adds New Relic License Key, New Relic Browser Key, New Relic User Key, New Relic Insights Query Key, New Relic Mobile App Token, Microsoft Teams Webhook V2, Figma Personal Access Token v3, and SolarWinds Observability detectors.
— Names all eight detectors but no usage detail.v3.97.0
1300
SharePoint historical version scanningnew40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Scans historical versions of SharePoint items, surfacing credentials that were removed from the current version but remain present in earlier versions of items in generic lists and search-driven document libraries.
— Explains scope but no configuration detail is given.product docs
1400
Android APK detection by content inspectionnew40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Detects Android package (APK) files by inspecting file contents rather than relying on the .apk extension, so packages surfaced through byte-stream enumeration are scanned.
— States the mechanism but no config or example.product docs
1500
Jira auto-close on remediationnew40how completely this was documenteddepth15/40specificity10/30actionability15/3040 / 100
Jira issues can now be configured, in integration settings, to close automatically when their underlying secret is remediated.
— Names the settings location but no field-level detail.product docs
1600
Location type filter on secrets list pageimproved40how completely this was documenteddepth15/40specificity10/30actionability15/3040 / 100
Adds a location type filter update on the secrets list page, consolidated into a single popover view that explains what is being filtered.
— Names the exact UI location but little mechanism.product docs
1700
S3 source custom endpoint supportnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds custom endpoint support to the S3 source, enabling scans against 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. storage services.
— Names the source and capability but no config example.v3.97.0
1800
Revoke access to a single shared secretimproved35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds the ability to revoke access to a single shared secret rather than revoking the entire share.
— Thin bullet with no UI or API path named.product docs
1900
Expired verified JWTs excluded from findingsimproved35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
Verified but expired JWTsJWTsJSON 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. are now excluded from findings at ingestion time, reducing noise from tokens that carry no remaining risk.
— Explains behaviour but no configuration or opt-out mentioned.product docs
2000
Editor-level notification triggeringimproved35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Editors can now trigger notifications directly, removing the previous dependency on admin-level access for routine notification workflows.
— States the permission change but no workflow detail.product docs
2100
Paginated user audit logimproved35how completely this was documenteddepth10/40specificity10/30actionability15/3035 / 100
The user audit log under Settings › Users now paginates, allowing navigation through long user histories.
— Exact UI path named but no further mechanism.product docs
2200
AWS Secrets Manager metadata typenew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds an AWS Secrets Manager metadata type for richer analysis output.
— Bare mention with no mechanism or example.v3.97.0
GitGuardian SaaS is a cloud-based security platform that detects and prevents secret leaks in Git repositories and source code.
GitGuardian shipped an API to set a custom validity status on secrets GitGuardian can't reach itself, an automated-detector option for custom source configuration, and a new Azure DevOps extension for one-click ggshield pipeline scanning.
└──▷ 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
Custom validity status API for secretsnew80how completely this was documenteddepth35/40specificity25/30actionability20/3080 / 100
A new API endpoint lets practitioners set a custom validity status (valid or invalid) on secrets from internal or private systems, requiring a personal access tokenpersonal access tokenA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. with the secrets:write scope. The status is displayed as Custom validity with the date it was set on every incident tied to that secret, surfaces in filters, severity and downstream incident workflows, and setting or removing it is recorded in both the incident activity log and the audit log.
Azure DevOps ggshield pipeline extensionnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
A new Azure DevOps extension lets admins add a ggshield secret scan job to every pipeline in their organization via a single pipeline decorator applied through Azure Pipelines.
— Names tool and mechanism but no setup steps givenproduct docs
0300
Detector-validators filter for custom sourcesnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
The public API now supports an Only use detectors with validators option when creating or updating custom sources, enabling fully automated and consistent source configuration.
CAPEv2 integrates Google Magika deep-learning content-type detection alongside libmagic for headerless and obfuscated file identification.
└──▷ USE IT
Enable Magika in your CAPE processing config to get deep-learning content-type labels on dropped files and decoded buffers that libmagic identifies only as data.
custom/conf/processing.conf
[magika]
enabled = yes
Adds [magika] section to processing.conf (via processing.conf.default) to enable/disable Google Magika content-type detection and tune confidence thresholds.
Adds get_magika() method to the FileObject class (lib/cuckoo/common/objects.py), returning a dict with label, description, mime_type, group, and score fields; runs below get_type() and never modifies the libmagic verdict.
Adds magika block to file info in CAPE's processing pipeline (modules/processing/CAPE.py), backfilling results for files retrieved from the MongoDB cache that predate Magika being enabled.
Adds clear_magika_cache() call at task boundaries in CAPE.py to prevent stale per-path predictions from persisting across tasks in long-lived workers.
Adds magika as a searchable hash/label type in the web search interface (search.html) and file info template.
+1 moreshow less
Adds lib/cuckoo/common/integrations/magika.py, a new integration module implementing magika_info() and MAGIKA_ENABLED using Google's ONNXONNXAn open file format for trained models, so a model built in one framework can run in another runtime or on other hardware. ONNX Runtime is the common engine that executes it.-based Magika model — particularly effective for detecting script types (PowerShell, Python) and headerless payloads where libmagic returns data / application/octet-stream.
ALEAPP v2026.3.0 adds SQLCipher decryption for Signal, deep Telegram artifact parsing, and more than a dozen new app and drone parsers, alongside expanded Samsung and Google system database support and a hardening pass on HTML report generation.
└──▷ WHAT SHIPPED ·
11 FEATURES0 OF 11 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
Stale-allowlist detection in claim language checkernew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds stale-allowlist detection and always-on NOT CHECKED reporting to admin/scripts/check_claim_language.py, closing a coverage-audit gap present in ALEAPP but not the other LEAPP cores.
— Names exact script path, a reader could run it directlyv2026.3.0
0200
Telegram for Android artifact parsingnew65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Adds Telegram for Android artifacts covering accounts, chats, peers, group/channel members, VoIP call logs, and service message actions parsed from cache4.db and shared preferences.
— Names source database and artifact scope, no runnable stepv2026.3.0
0300
Snapchat arroyo.db conversation recoverynew65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Adds Snapchat arroyo.db conversation parsing, including recovery of WALWALWrite-Ahead Log: a durability mechanism in databases where changes are recorded to an append-only log before being applied to main storage, giving tools crash recovery and atomic transactions without full-page rewrites.-only rows with row-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. columns.
— Names database and recovery mechanism, no usage steps givenv2026.3.0
0400
Signal for Android decryption and message linkingnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Adds Signal for Android parsing with full SQLCipher decryption, attachment and thumbnail decryption, and message-linking.
— Names SQLCipher and mechanism but no exact command or pathv2026.3.0
thinner coverage below
0500
New app and drone artifact parsers across a dozen appsnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds new parsers for Session (account parsing from shared preferences), Kik, BeReal (from app caches), JusTalk and JusTalk Kids (from the Realm store and MMKVMMKVA key-value storage library from Tencent, built on memory-mapped files, that gives apps fast persistent storage without explicit write calls — useful for tools that need low-latency local state or config caching. stores for account identity and app state), Weibo (including bidirectional image-to-post linking), Xiaohongshu (RED), Slack, AllTrails, BRD (BreadWallet), Dropbox, what3words (via a vendored Realm parser), DJI drone flight tracks, Claude, MeWe (posts, comments, media, polls, reactions, and groups), and Smart Sidebar File Dock artifacts for OxygenOS/ColorOS.
— Each addition described in one line, no depth beyond namesv2026.3.0
0600
Google Play services database parsingnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds Google Play services database parsing covering constellation, account history, icing, and ODLH databases.
— Named databases but no parsing detail or usage stepv2026.3.0
0700
Samsung system database parsingnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds Samsung system database parsing covering Privacy Dashboard, WiFi, Sleep Detection, CMH tagging, and media provider.
— Named sub-areas but no mechanism or usage detailv2026.3.0
0800
HTML report injection and remote destination hardeningimproved55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds a CI guard for HTML report injection and remote destinations; evidence names are now escaped in report media tags and all remote CDNCDNA content delivery network, servers distributed across locations that cache and serve content near readers. It can reduce loading time and traffic to the original server./URL destinations removed from HTML reports.
— Explains the fix mechanism, no config key or command givenv2026.3.0
0900
ProtonVPN offline hostname resolutionimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
ProtonVPN hostname resolution no longer touches the network at parse time.
— States the behavior change but no further mechanismv2026.3.0
1000
Modernized UsageStats and Recent Tasks parsingimproved25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds modernized UsageStats and Recent Tasks artifact parsing.
— Bare description, no explanation of what changedv2026.3.0
1100
Google Dialer and Calendar artifact parsingnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds Google Dialer and Google Calendar artifact parsing.
— Bare name of two apps, no further detailv2026.3.0
iLEAPP v2026.3.0 adds Apple Unified Logs support and a rotated PowerLog archive parser that extends recoverable history by weeks, alongside new parsers for Telegram, Wickr, Session/Oxen, and seven other apps.
└──▷ 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
Telegram artifact parsing for iOSnew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds Telegram artifacts for iOS: Accounts (from accounts-metadata/atomic-state and Postbox t0), Contacts & Peers (full t2 peer dump with avatar images and Spotlight cache), Chats (Postbox chat list), Cached Peer Details (Postbox t18), Device Contacts (Postbox t54), Peer Presence, and Message Tags.
— Names every underlying database table and source path.v2026.3.0
0200
Rotated PowerLog archive (PLSQL.gz) parsingnew75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
Adds parsing of *.PLSQL.gz rotated PowerLog archives, decompressed to a session temp directory and reused across all PowerLog artifacts, alongside the existing CurrentPowerlog.PLSQL, with per-archive time-offset correction that extends recoverable history by weeks on most images.
— Names exact file formats and correction mechanism, no CLI step given.v2026.3.0
0300
Wickr artifact and identity recoverynew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds Wickr artifacts parsed from wickrLocal.sqlite and app logs, plus Wickr account identity recovered from the keychain.
— Names source database and keychain recovery, no exact fields.v2026.3.0
thinner coverage below
0400
New app parsers for DuckDuckGo, MEGA, Onion Browser, what3words, Dubox/Terabox, Claude, Apple Intelligence Report, and Lidl Plusnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds new app parsers for DuckDuckGo, MEGA, Onion Browser (including Realm-based artifacts via a vendored Realm parser), what3words, Dubox/Terabox, Claude, Apple Intelligence Report, and Lidl Plus (SQLCipher + Keychain).
— Names each app and two decryption mechanisms, no field-level detail.v2026.3.0
0500
Apple Unified Logs supportnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds Apple Unified Logs support with the parser bundled into all builds, surfacing 16+ new artifacts identified from a predicate survey.
— States scope and count but not which artifacts.v2026.3.0
0600
CI hardening and expanded test coveragenew45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
Adds a CI tripwire guarding against unsupported claim language in artifact documentation, a CI guard for HTML report injection and remote destinations in generated reports, and CI test coverage for the Python 3.13 and 3.14 runtime contract plus Windows/Linux/ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead. test builds.
— Describes CI scope but not user-facing usage.v2026.3.0
0700
Biome/SEGB coverage for edge selection, notifications, privacy accounting, and contact feedbacknew40how completely this was documenteddepth15/40specificity20/30actionability5/3040 / 100
Adds Biome/SEGB coverage for Networking Edge Selection, DuetExpertCenter notifications, Privacy Accounting streams, and Contact Autocomplete Feedback.
— Names four artifact areas without mechanism or format.v2026.3.0
0800
Session/Oxen artifact parsingnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Adds Session/Oxen artifacts including decrypted messages, contacts, and attachments.
— Thin description, no source file or mechanism named.v2026.3.0
Finite State Platform is a software supply chain security tool that analyzes firmware and software components for vulnerabilities and compliance risks.
Finite State added an in-product What's New drawer for release highlights and made targeted reliability and usability fixes to license search and the License Policy page.
└──▷ 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
License search and policy page improvementsimproved60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Improves license search so prefix matches appear before substring matches in the Add Licenses and Component license pickers, and updates the License Policy page to source the live license catalog and display a retryable error state when the catalog cannot load.
Edit and replay captured network traffic at arbitrary speeds — a suite of pcap tools for *NIX and Windows.
tcpreplay 4.6.1 focuses on testing infrastructure — continuous OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees.-Fuzz fuzzing, UBSan hardening, and a new unit test suite — while removing the --xdp-batch-size flag.
└──▷ WHAT SHIPPED ·
4 FEATURES1 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
Continuous OSS-Fuzz fuzzing pipelinenew73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Adds three libFuzzer targets under test/fuzz/ — fuzz_pcap, fuzz_fragroute, and fuzz_services — built against ASan/UBSan and submitted to OSS-Fuzz for continuous fuzzing of the pcappcapA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. parser, the fragroute rules engine, and the tcpprep --services parser.
— Names exact fuzz targets and paths but no run instructionsv4.6.1
0200
Dependency-free unit test suitenew65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Adds a dependency-free unit test suite under test/unit/, runnable via make check or ctest.
Removal of --xdp-batch-size flagbreaking50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
The --xdp-batch-size flag has been removed; any script or config that passes it will fail on upgrade.
— Names exact flag and upgrade impact, no migration path givenv4.6.1
0400
UBSan checks and packed wire-format structsimproved48how completely this was documenteddepth25/40specificity18/30actionability5/3048 / 100
UBSan now runs alongside ASan in CI to catch misaligned-access bugs, and wire-format header structs are now marked packed, hardening packet parsers against a class of defects ASan alone misses.
— Explains mechanism but is internal CI/build changev4.6.1
└──▷ BREAKING ON UPGRADE
!
The --xdp-batch-size flag has been removed; any script or config that passes it will fail on upgrade.
Sublime Security is an email security platform that detects and prevents advanced threats like phishing, malware, and business email compromise attacks.
Sublime Security introduced Tailored Phishing Simulations in Beta, a new capability for running environment-aware phishing campaigns with staggered delivery and cross-campaign tracking.
└──▷ 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
Tailored Phishing Simulations (Beta)new65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
New beta feature lets teams run phishing campaigns prioritized by the attack patterns Sublime is already detecting in the customer's environment. Campaigns support sending multiple templates per campaign with staggered delivery schedules, and a cross-campaign dashboard tracks click rates, report rates, and repeat clickers with recipient-level detail per campaign. Available to all customers during Beta; at GA it will move to a paid Sublime Tailored Phishing Simulations and Training add-on, enabled by contacting Sublime Support.
eksctl v0.230.0 adds FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments.-compliant Bottlerocket support for managed nodegroups, introduces control plane component configuration, and relaxes required addons for IPv6IPv6The current version of the Internet Protocol, standardized by the IETF, using 128-bit addresses to replace the exhausted IPv4 space. Cyber tools target it because modern networks run dual-stack or IPv6-only. clusters.
└──▷ 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
BottlerocketFips AMI family for managed nodegroupsnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds BottlerocketFips AMI family support in managed nodegroups, enabling FIPS-compliant Bottlerocket nodes.
— Names the AMI family but no config example givenv0.230.0
0200
Optional vpc-cni and kube-proxy for IPv6 clustersimproved55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Makes vpc-cni and kube-proxy optional when creating IPv6 clusters, reducing mandatory addon installation.
— Names the two addons and the cluster type affectedv0.230.0
0300
Control plane component configurationnew35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds control plane component config support, enabling configuration of individual EKS control plane components.
— No specifics on which components or config keysv0.230.0
Sysdig Secure is a container security platform providing runtime monitoring, vulnerability scanning, and compliance enforcement for cloud-native applications.
Sysdig Secure ships image layer-level vulnerability attribution across the Findings and Resource Details views, plus a new Vulnerability Policies evaluation tab and base image allow/deny list rules for rule bundles.
└──▷ 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
Per-layer vulnerability analysis for container imagesnew75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
Adds a Layers tab in the Resource Details drawer for container images, listing every layer grouped by base image or Application Layers, with the Dockerfile instruction and per-severity vulnerability counts for each layer; selecting a layer filters the Vulnerabilities tab. Adds a Layer filter on the Findings view to slice the CVE list by a specific image layer directly. Adds Layer Number and Layer Command fields to the Findings Details drawer and findings panel showing which layer and Dockerfile instruction (e.g. RUN apt-get install -y curl) introduced the affected component — selecting the Layer Command opens the Layers tab for deeper inspection.
Base image allow/deny list rulesnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds Base Image Allow List and Base Image Deny List rules under Image Configuration in rule bundles, accepting base image pull strings to approve or block entire registries or namespaces in a single entry.
Vulnerability Policies tab in Resource Details drawernew65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds a Vulnerability Policies tab in the Resource Details drawer, opened from Vulnerability Findings, showing how each resource was evaluated against configured Vulnerability Policies. A details panel per rule surfaces CVEs, affected components, and remediation guidance, and exceptions can be created directly from the drawer.
Google SecOps is a unified security operations platform combining threat detection, investigation, and response capabilities across cloud and enterprise environments.
Google SecOps gains Cloud Logging integration for 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 pipeline monitoring and feed debugging (public preview, BYOP required).
└──▷ HOW TO FIND IT
Quickly jump from a failing feed to its pre-filtered Logs Explorer view to diagnose missing or delayed log delivery.
📍In the Google SecOps console, go to Feed management, locate the feed you want to debug, and select Debug with logs to open Logs Explorer pre-filtered for that feed.
Iru shipped phased OS rollouts for Apple devices, an authenticated guest mode for SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management., and upfront compliance framework selection in Compliance Automation.
└──▷ 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
Phased rollouts for Apple OS updatesnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Managed OS for Apple devices now supports phased rollouts, enabling staged OS update deployments across a fleet rather than pushing updates to all devices at once.
Cribl is a data processing and routing platform that collects, transforms, and delivers security and observability data from multiple sources.
Cribl added OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor.-based instrumentation for Pydantic AI into its 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. Observability pipeline, and shipped a new Privacy 2.1 model family that scans telemetry faster and with less memory in Cribl Guard.
└──▷ 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
Cribl Privacy 2.1 detection model familyimproved80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Cribl Privacy 2.1 introduces a new AI-based telemetry privacy detection model family for Cribl Guard, delivering 64%–163% higher detection throughput and 13%–24% lower average memory use versus Privacy 2.0, with F1 accuracy held steady or improved and CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. utilization unchanged. A new model pruning and distillation pipeline shrinks feed-forward layers by 75% or more and trains a smaller student model against the original frozen teacher to recover near-equivalent detection quality at higher throughput. It introduces a three-tier lineup — Fast (maximum throughput), Base (balanced), and Pro (maximum detection accuracy, coming soon) — so operators can pick an accuracy/throughput/resource tradeoff per pipeline, trained on data enriched with feedback from production Guard customers. It also previews cribl-privacy-3.0-pro, a forthcoming larger, high-accuracy model for lower-volume, accuracy-sensitive workloads, alongside additional personalization controls for tuning detections per environment.
Tenzir is a security data platform that ingests, transforms, and analyzes security telemetry and threat intelligence data.
Tenzir v6.11.0 ships a new merge operator, parallel pipeline execution, and extended windowing, alongside full Sigma v2.1 detection support with 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. Detection Findings output, new YARA-X detection findings, summarize eventstats/streamstats modes, and new geo, math, and string functions.
└──▷ WHAT SHIPPED ·
10 FEATURES3 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
Window operator gains new modesimproved95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Extends window operator with processing-time (omit on), count-based (unsigned size), and trailing windows (trailing=true), exposing the triggering event through $window.event; adds a trigger expression to selectively fire subpipelines and tolerance for bounded reordering of late events.
Compute a rolling 5-minute byte sum that travels with each event, enabling streamstats-style enrichment without leaving the pipeline.
Full Sigma v2.1 rule support in sigma operatornew95how completely this was documenteddepth40/40specificity30/30actionability25/3095 / 100
Adds path= and rules= named arguments to the sigma operator — path= accepts a file, directory, or mixed list (searched recursively) and rules= embeds YAML rule strings directly in a pipeline, with positional path now deprecated — and implements the full Sigma v2.1.0 detection rule surface, including exists, cased, neq, windash, fieldref, UTF-16 encoding modifiers, re sub-modifiers i/m/s, time-part modifiers minute through year, list-form OR conditions, and global filter rules targeting rules by id or name (or rules: any for all compatible sources). Also adds tenzir.metrics.sigma events emitted per batch reporting input event count, rule evaluations, and matches, and Sigma matches now output as OCSF Detection Findings.
Sigma engine breaking behavior changesbreaking85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Passing a rule path positionally to the sigma operator now emits a deprecation warning (use path= instead); several Sigma modifiers that were previously silently misinterpreted now match correctly, changing results for rules relying on the old behavior; Sigma wildcards now treat all regex metacharacters literally and match across newlines (so a+b no longer accidentally matches ab); field names containing dots now deterministically prefer an exact top-level key before nested traversal; and Sigma rules with custom taxonomies or expand placeholder expansion are now rejected with an explicit diagnostic instead of being silently accepted.
— Clear before/after behavior but no migration command givenproduct docs
0400
Parallel pipeline executionnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Enables parallel pipeline execution via a // parallelism: <n> leading comment or the --parallelism flag on the tenzir binary, running CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware.-bound operators across multiple cores while preserving per-operator semantics.
summarize operator eventstats and streamstats modesnew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds output: 'events' option to the summarize operator to attach final aggregate values to every event in a finite input (TQL equivalent of Splunk eventstats), and adds an incremental summarize output for running aggregates on event streams (cumulative event emission for unbounded streamstats-style use cases).
exp, log, and pow math functionsnew65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Adds exp(), log(), and pow() math functions to TQL; log() defaults to the natural base and accepts an optional second argument for arbitrary logarithm bases.
Dynamic patterns in replace functionimproved65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Extends replace function to accept dynamic patterns and replacements (e.g. message.replace(user.name, '<redacted>')); literal calls with an empty pattern leave the subject unchanged.
Passing a rule path positionally to the sigma operator now emits a deprecation warning; use path= instead.
!
Several Sigma modifiers that were previously silently misinterpreted now match correctly, meaning rules relying on the old incorrect behavior will produce different (corrected) results.
!
Sigma wildcards now treat all regex metacharacters literally and match across newlines, so patterns such as a+b no longer accidentally match ab.
!
Field names containing dots in Sigma rules now deterministically prefer an exact top-level key before nested traversal, changing resolution behavior for ambiguous field names.
!
Sigma rules with custom taxonomies or that use expand placeholder expansion are now rejected with an explicit diagnostic rather than silently accepted.
OpenCVE v3.1.0 introduces a 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. v2 with OpenAPIOpenAPIA vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. documentation and scoped tokens, adds project-level access control with membership roles, and extends organization audit logging.
└──▷ WHAT SHIPPED ·
4 FEATURES2 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.
0101
REST API v2 with OpenAPI docsnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
OpenCVE ships a new REST API v2 with OpenAPI documentation and scoped tokens for integrations. An API Docs link is now visible to all users in the header for easy access to the new documentation.
— Names API version and docs but no endpoint paths given.v3.1.0
0202
Project-level access control and membership rolesnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
OpenCVE adds project-level access control with membership roles and enforced ACLsACLsAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource. across CVE views and dashboard widgets, plus a new project members management UI for administering per-project roles.
— Explains scope and enforcement points, includes UI location.v3.1.0
thinner coverage below
0300
Access mode and scopes for org API tokensimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Organization API tokens gain an access mode and fine-grained scopes, enabling tighter permission control on existing org-level tokens, alongside an improved organization API token management UI.
— Describes new controls but no concrete scope names or config keys.v3.1.0
0400
Extended organization audit logsimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Organization audit logs now cover automations, CVE comments, and project membership changes.
— Lists new log categories but no mechanism or access path.v3.1.0
Didit is a decentralized identity verification platform enabling secure, privacy-preserving credential management and verification across applications.
Didit's changelog this window centers on richer Session API data and verification branching, alongside expanded error signaling and React Native SDK compatibility.
└──▷ 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
Barcode fields in Session APInew67how completely this was documenteddepth20/40specificity22/30actionability25/3067 / 100
The Session API now returns barcode data extracted from scanned ID documents, exposed via id_verifications[].barcodes in the session response returned by GET /v1/sessions/<session_id>.
Inspect barcode data extracted from a scanned ID document after a verification session completes.
502 error codes for KYB and phone checksnew38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
New 502 error codes have been added for 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. (Know Your Business) and phone verification flows to signal these check failures more clearly.
Nudge Security monitors SaaS application usage and security risks across organizations to reduce cloud infrastructure threats.
Nudge Security launched a new Risk dashboard (open beta) that consolidates business criticality and residual risk scoring into a single view of 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. risk posture.
└──▷ 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
Risk dashboard with trend chart and risk matrixnew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
A new Risk dashboard at Dashboards > Risk (open beta) shows tiles for apps assessed, business-critical apps, overall residual risk, and apps missing approval, built automatically from Nudge's business criticality tiers and residual risk scores. It includes a risk trend chart that can be filtered to business-critical apps only over time, a business criticality vs. residual risk matrix where clicking any cell reveals the exact apps behind that risk concentration, and a highest-risk apps ranking table ordering apps by risk score so reviewers can see what needs attention first.
Review your SaaS risk posture and identify apps missing approval or carrying high residual risk.
📍In the Nudge Security console, go to Dashboards › Risk to view tiles for apps assessed, business-critical apps, overall residual risk, and apps missing approval.
DigiCert CertCentral is a platform for managing SSL/TLS certificates, automating issuance, renewal, and deployment across organizations.
DigiCert CertCentral's biggest changes this window are compliance-driven: shorter certificate validity and reuse windows, mandatory CT logging, DNSSECDNSSECA set of DNS extensions, maintained by the IETF, that add cryptographic signatures to DNS records so resolvers can verify responses have not been tampered with in transit. enforcement during DCVDCVDomain Control Validation, a certificate-authority process that proves an applicant controls a domain before issuing a TLS certificate; cyber tools use it to automate certificate provisioning workflows./CAA checks, and stricter Multi-Perspective Issuance Corroboration, alongside the retirement of legacy ACMEACMEAn IETF-standard protocol (RFC 8555) for automating TLS certificate issuance and renewal, letting cyber tools manage certificates without manual CA interaction., CertCentral Discovery and Managed Automation, plus smaller usability additions like CSRCSRA Certificate Signing Request is a block of encoded data submitted to a certificate authority, containing a public key and identity details, so the CA can issue a signed TLS certificate without ever seeing the private key.-driven CN/SANs population and new DCV polling status fields in the Services API.
└──▷ WHAT SHIPPED ·
12 FEATURES8 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.
0100
DCV polling status in Services APInew88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
Adds dcv_polling_status and dcv_polling_last_checked fields to the Services API responses for certificate requests and DNS name validations, surfacing whether DigiCert's automatic DCV polling is active and when it last ran.
Check whether DCV polling is active and when it last ran for a pending certificate order, to decide whether to trigger a manual validation check.
json
// Example Services API response fragment for a pending order
{
"dcv_method": "dns-txt-token",
"dcv_token": {
"token": "{{dcv_token}}",
"status": "pending",
"expiration_date": "2022-02-24T16:25:52+00:00"
},
"dcv_polling_status": true,
"dcv_polling_last_checked": "2026-07-09T22:07:24Z"
}
Use CN/SANs from CSR on certificate requestsnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds a Use CN/SANs from CSR option on certificate request forms (DV, OV, EV TLS; QWAC and QWAC PSD2; X9 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. for TLS; Private TLS) to replace existing Common Name and SANs fields with values from the uploaded CSR, with an Undo option to revert.
Mandatory CT logging for public TLS certificatesbreaking70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Removes CT logging opt out options from CertCentral, enforcing CT logging on all public TLS certificates (DV, OV, EV, QWAC, QWAC PSD2) across all DigiCert brands. Certificates that previously needed to be kept out of CT logs can no longer be issued that way from June 1, 2026 onward.
Certificate validity and validation reuse periods reducedbreaking70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Moves public TLS certificate maximum validity to 199 days and public code signing certificate maximum validity to 459 days, and reduces domain validation and organization validation reuse periods to one day less than the CA/Browser Forum permitted maximums, per CA/Browser Forum requirements. Orders requesting longer validity periods will be rejected or truncated.
DNSSEC validation during DCV and CAA checksbreaking65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Begins DNSSEC validation during domain control validation and DNS CAA checks, returning DNSSEC-specific error and status messages in CertCentral order details pages and via the Services API when issues are detected. Domains with misconfigured DNSSEC will block certificate issuance until the configuration is resolved.
Stricter Multi-Perspective Issuance Corroborationbreaking65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Updates Multi-Perspective Issuance Corroboration (MPICMPICMulti-Perspective Issuance Corroboration, a CA/Browser Forum requirement that certificate authorities verify domain control from multiple network vantage points to reduce BGP hijack and DNS manipulation risks during certificate issuance.) to require corroboration from at least four remote network locations across at least two different Regional Internet Registry regions. Certificate issuance fails if more than one perspective does not corroborate.
Legacy CertCentral ACME service retirementbreaking60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Retires the legacy CertCentral ACME service, with legacy ACME credential warnings shown in the ACME credentials table and requests to legacy ACME URLs failing to issue certificates after the retirement date. Legacy credentials must be replaced with new CertCentral ACME credentials.
CertCentral Discovery and Managed Automation retirementdeprecated55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Announces retirement of CertCentral Discovery and Managed Automation services on October 1, 2026, with capabilities moving to DigiCert Trust Lifecycle Manager. Integrations relying on these services will stop working after that date.
Simplified delegation request workflowimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Removes the organization selection step from the delegation request workflow — a single delegation request now applies to all organizations the selected approver represents and all certificate products they are authorized to approve.
Client Authentication EKU removed from public TLS certsbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Public TLS certificates will no longer be issued with the Client Authentication EKU; existing workflows that depend on this EKU on newly issued certificates will break.
Editable Service User namesimproved35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Enables updating a Service User's first and last names in CertCentral, making it easier to distinguish Service Users and assign them to teams or operational roles.
Public TLS certificates will no longer be issued with the Client Authentication EKU; existing workflows that depend on this EKU on newly issued certificates will break.
!
CT logging opt-out options are removed from CertCentral — certificates that previously needed to be kept out of CT logs can no longer be issued that way from June 1, 2026 onward.
!
Requests to legacy ACME URLs will fail to issue a certificate after the legacy CertCentral ACME service retirement date; legacy credentials must be replaced with new CertCentral ACME credentials.
!
CertCentral Discovery and Managed Automation services retire on October 1, 2026 — integrations relying on these services will stop working.
!
TLS certificate validity is capped at 199 days and code signing certificate validity at 459 days; orders requesting longer validity periods will be rejected or truncated.
!
DNSSEC validation is now enforced during DCV and CAA checks — domains with misconfigured DNSSEC will block certificate issuance until the configuration is resolved.
!
MPIC now requires corroboration from at least four remote network locations across at least two RIR regions — certificate issuance fails if more than one perspective does not corroborate.
Twingate is a zero-trust network access platform that securely connects remote users and devices to private resources without VPN.
Twingate extended its Identity Firewall to protect internal HTTP web apps, authenticating users at the Twingate layer before they reach the app.
└──▷ 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
HTTP web app support in Identity Firewallnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Twingate Identity Firewall now supports HTTP web apps, enabling protection of internal web apps, data portals, CI/CD infrastructure, and AI-coded business apps. It authenticates users at the Twingate layer using 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. and custom header injection, supporting 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., JITJITA runtime compilation strategy where code is translated from an intermediate form to native machine instructions at execution time, giving tools the speed of compiled code without sacrificing dynamic flexibility. access, security policies, and access logging, so users reach internal web apps already authenticated.
Firezone is an open-source VPN and secure access platform that replaces traditional corporate VPNs with modern zero-trust networking.
Firezone's macOS/iOS client gains a command-line interface aimed at unattended or remotely managed Macs.
└──▷ 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
New `firezone-cli` for macOS Clientnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Adds firezone-cli, a command-line interface to the macOS Client intended for Macs that run unattended or are managed remotely.
RegScale is a compliance and regulatory management platform that automates governance, risk, and compliance (GRC) workflows for organizations.
RegScale 6.33.1.0 expands AI Agent coverage to Lines of Inquiry, CAPs, Risk Treatment, Questionnaire Scoring, and more.
Extends AI Agent capabilities to Lines of Inquiry, Corrective Action Plans, Risk Treatment Mappings, Questionnaire Scoring, Lightning Assessment Tests, and Security Control Test Generation.
Adds RegML Mapping Recommendations (details not fully disclosed in release notes).
Daytona is a development environment platform that enables standardized, reproducible coding spaces for teams and AI agents.
Daytona 0.201.0 adds direct 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. file transfers via pre-signed sandbox URLs, along with typed SDK error codes and a date-range filter for sandbox listing.
└──▷ 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
Pre-signed sandbox file transfer URLsnew50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Introduces pre-signed sandbox file download and upload URLs, allowing direct S3-compatible file transfers without proxying through the API.
— Explains mechanism but no exact API call or flag givensnapshot-20260815
0200
Sandbox list date-range filternew20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
Adds a date-range filter to the sandbox list functionality, per the release summary, with no further detail on parameters or endpoint given.
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.233 adds GitLab merge request support, an opt-in apps gateway identity-forwarding setting, a Linux memory limit for Bash tool commands, and a WebFetch cache TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. knob, while also disabling todo/task-tracking tools by default on newer models.
└──▷ WHAT SHIPPED ·
11 FEATURES1 OF 11 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
Todo/task-tracking tools disabled by default on newer modelsbreaking85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
Todo/task-tracking tools (TaskCreate, TaskGet, TaskUpdate, TaskList, TodoWrite) are no longer available by default on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models; set CLAUDE_CODE_ENABLE_TODO_TOOLS=1 to restore them.
Re-enable todo/task-tracking tools on newer models that disable them by default.
$ CLAUDE_CODE_ENABLE_TODO_TOOLS=1 claude
— Names exact tools, affected models, and restore command.v2.1.233
0200
Memory limit for Bash tool commandsnew82how completely this was documenteddepth30/40specificity22/30actionability30/3082 / 100
Adds the CLAUDE_CODE_TOOL_MEMORY_LIMIT environment variable (Linux only) to cap memory for Bash tool commands via cgroup support, preventing a runaway build from stalling a session.
Cap memory for Bash tool commands on Linux to prevent a runaway build from consuming all RAMRAMWorking memory that holds programs and data while a computer is running. Its contents usually disappear when power is removed. and stalling the session.
$ CLAUDE_CODE_TOOL_MEMORY_LIMIT=2G claude
— Named env var with runnable example and cgroup mechanism.v2.1.233
0300
WebFetch cache TTL controlnew72how completely this was documenteddepth22/40specificity20/30actionability30/3072 / 100
Adds the CLAUDE_CODE_WEBFETCH_CACHE_TTL_MS environment variable to control the WebFetch session URL cache TTL, defaulting to 15 minutes.
Shorten the WebFetch URL cache lifetime so repeatedly-fetched pages stay fresh during a long session.
$ CLAUDE_CODE_WEBFETCH_CACHE_TTL_MS=300000 claude
— Named env var, default value, and runnable example.v2.1.233
0400
GitLab merge request support in worktree and agents viewimproved65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Extends the --worktree flag and the claude agents view to accept GitLab merge request URLs, displaying MRs as !N.
— Names flag, view, and display format for MRs.v2.1.233
0500
Skills directory validation in plugin validateimproved65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Improves claude plugin validate to inspect a bare .claude/skills directory and report SKILL.md files with unparseable frontmatter.
— Names command and directory/file targets.v2.1.233
0600
Per-user identity forwarding on apps gatewaynew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds an opt-in forward_user_identity apps gateway setting on Anthropic upstreams, forwarding the signed-in user's identity as headers so a proxy can attribute spend per user.
— Named setting and purpose, but no exact config path shown.v2.1.233
0700
Unrecognized model diagnostic in print modenew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds a [claude-code:unrecognized_model] diagnostic line to stderr in print mode when a request is sent for an unrecognized model ID; suppress it with modelOverrides.
— Exact diagnostic string and suppression key named.v2.1.233
0800
Apps gateway upstream error forwardingimproved60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Improves apps gateway error forwarding so 400/413 responses from Vertex, Foundry, and Claude Platform on AWS upstreams now surface the upstream's own error message.
— Names upstreams and status codes but no user action.v2.1.233
thinner coverage below
0900
Faster self-hosted-runner session startimproved55how completely this was documenteddepth30/40specificity15/30actionability10/3055 / 100
Improves claude self-hosted-runner session start time by creating the session branch without rewriting the working tree and eliminating two blocking server round trips.
— Mechanism described but no numbers or user action.v2.1.233
1000
Screen reader mode improvementsimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
The /effort selector now renders as a numbered list with a typed-number prompt, and hint and dialog text is no longer clipped in screen reader mode.
— Names the /effort selector as a starting point.v2.1.233
1100
GitHub app setup tip suppressed for non-GitHub hostsimproved45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
Suppresses the GitHub app setup tip in repositories whose origin remote is on gitlab.com or bitbucket.org; the enterprise marketplace tip now covers non-GitHub internal git hosts.
— Named hosts but purely cosmetic, no action needed.v2.1.233
└──▷ BREAKING ON UPGRADE
!
Todo/task-tracking tools (TaskCreate, TaskGet, TaskUpdate, TaskList, TodoWrite) are no longer available on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models; set CLAUDE_CODE_ENABLE_TODO_TOOLS=1 to restore them.
Lightweight coding agent that runs in your terminal
OpenAI Codex CLI's alpha builds this window centered on Guardian V2 risk scoring and its new configuration surface, defaulted unified exec on Windows, expanded gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. code-mode 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. protocol handling, and added thread usage monitoring alongside numerous smaller reliability and telemetry changes.
└──▷ WHAT SHIPPED ·
0 FEATURES17 FEATURES2 OF 17 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
Guardian V2 risk classification and scoringnew88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
Guardian V2 introduces risk scoring on threads that flags high-risk actions for automatic review, recording scores as snapshots, initializing per-thread samplers, and preserving transcript boundaries. features.guardianv2 now accepts either a boolean toggle or an object configuring classifier instructions, review threshold, reasoning effort, action and instruction token limits, transcript source inclusion, per-entry and total token budgets, and the number of recent non-user entries.
Unified exec enabled by default on Windowsbreaking75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
unified_exec is now enabled by default on all platforms including Windows, exposing exec_command and write_stdin on Windows instead of the previous shell_command.
Thread usage monitoring in status and terminal titlenew73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
Adds thread-credits and estimated-thread-cost as configurable terminal title items for monitoring per-thread quota consumption, shows estimated thread usage in the /status command 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. status surfaces, and adds per-thread usage queries to the backend client.
gRPC code-mode host support in app serverimproved65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
The app server now supports gRPC code-mode hosts alongside existing WebSocketWebSocketA protocol that upgrades an HTTP connection into a persistent, full-duplex channel, letting a server push data to a client without repeated polling. Cyber tools use it for real-time event streaming and live command output.-based hosts, and removes the gRPC code-mode open session limit so a host can register more than MAX_IN_FLIGHT_REQUESTS open sessions simultaneously.
agent_name in Responses API turn metadatanew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds agent_name to Responses API turn metadata, falling back to /root when no canonical agent path is set, with the field reserved from client metadata overrides.
MCP server protocol discovery and header customizationimproved63how completely this was documenteddepth25/40specificity28/30actionability10/3063 / 100
MCP servers gain dynamic HTTP header helpers enabling per-request header customization, and MCP client protocol discovery is now instrumented with a counter and duration metric tagged legacy or auto mode and classified as modern, legacy, or failure outcomes.
Strict auto-review for MCP tool callsbreaking50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Codex now enforces strict auto-review for MCP tool calls even when the approval policy, tool annotations, or a remembered session decision would otherwise skip review.
tool_search for plugin app discoverynew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
The model is now instructed to use tool_search to discover relevant tools within a selected plugin's apps before falling back to unrelated or built-in tools.
MCP connection reuse during reconciliationimproved45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
Reuses active, uncancelled pending MCP connections during reconciliation when identity, catalog limit, and protocol mode still match, avoiding redundant startups.
Workload identity integration for authenticationnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Integrates workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. with Codex authentication for enterprise environments.
Model ETag tracking via WebSocket metadataimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Reads model ETagsETagsHTTP response headers that identify a specific version of a resource, letting clients skip re-downloading unchanged content; cyber tools use them to detect when monitored assets have been silently modified. from WebSocket metadata events for more efficient model version tracking.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline added web search for supported models across its extension and desktop app, introduced a font size slider in desktop Settings, and expanded its model catalog with Crusoe as a new provider alongside updated per-provider default models.
└──▷ 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
Web search for supported modelsnew65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds a Web Search toggle in Settings (desktop) and Feature Settings (extension/CLI) that lets supported models search the web during a task; search calls and results are recorded in the session transcript/conversation and persist across reopens and reloads.
Font size slider in desktop Settingsnew55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds an app font size slider in Settings that scales the interface and applies the chosen size before the window paints, eliminating the flash-to-old-size on launch.
— UI path clear, no config key or default valuedesktop-v0.0.13
0300
Crusoe model provider and catalog updatesnew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds Crusoe as a new model provider in the catalog, alongside updated model lists and per-provider default models across all existing providers.
Pi's v0.84.2 release (mirrored across several docs updates) bundles fullscreen transcript search, granular tool-selection controls, per-run theming, SDK model-catalog caching with offline mode, and new extension/gateway APIs.
└──▷ WHAT SHIPPED ·
12 FEATURES0 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.
0100
Model catalog caching and offline mode in SDKnew91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
ModelRuntime.create() now accepts allowModelNetwork and modelRefreshTimeoutMs to opt into a network refresh of the model catalog at creation time and bound how long it may take, plus modelsStorePath to set a custom local catalog store path and a modelsStore injection point for a custom persistence implementation. A new modelRuntime.refresh({ allowNetwork: true, force: true, signal }) method forces an immediate catalog refresh, bypassing the default four-hour per-provider throttle, and the PI_OFFLINE environment variable disables all model network access.
Refresh the model catalog at startup with a 15-second timeout — useful in CI or containerized environments where stale catalogs would cause failures.
Force an immediate catalog refresh mid-session, bypassing the four-hour throttle — useful after a provider publishes a new model you need right away.
javascript
await modelRuntime.refresh({ allowNetwork: true, force: true, signal });
— Full API surface named with runnable examplesproduct docs
0200
Tool selection controls: defaultTools and CLI flagsnew88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
A new defaultTools config key selects which built-in tools are enabled at startup (e.g. ["bash", "edit", "write"], or an empty array for none), while extension and SDK custom tools remain enabled regardless. New CLI flags refine this: --tools acts as a strict allowlist for all tools (replacing defaultTools behavior), --no-tools disables all tools, --no-builtin-tools disables only built-in defaults, and --exclude-tools filters the resulting tool list after other tool flags are applied.
Start Pi with only bash and edit available at launch, keeping any extension tools active — useful for restricting the default toolset in a project.
json
{"defaultTools": ["bash", "edit"]}
Set the default built-in tool selection for all projects globally so every new session starts with only the tools you want.
json
{
"defaultTools": ["read", "bash"]
}
— Every flag and config key named with examplev0.84.2
0300
Per-run theme selection with --use-theme flagnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
The --use-theme flag starts an interactive run with a specific theme without changing the saved setting, e.g. pi --use-theme light, and supports light/dark syntax such as pi --use-theme light/dark to follow the terminal's appearance for that run.
Start a single session with the light theme without overwriting your saved theme preference.
$ pi --use-theme light
Follow the terminal's light/dark appearance for one run without changing the saved setting.
$ pi --use-theme light/dark
Apply a specific theme for a single Pi session without overwriting your saved theme preference.
$ pi --use-theme dark/compact
Lock in a specific visual theme for a single interactive session without overwriting your saved preferences.
$ pi --use-theme dracula interactive
Apply a one-off theme for a single session without permanently changing your saved theme preference.
$ pi --use-theme dracula
— Exact flag and syntax with runnable commandsv0.84.2
0400
Fullscreen transcript search and scrollingnew78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Fullscreen mode gains transcript search via Ctrl+Shift+F with incremental match highlighting and next/previous navigation using Enter/Ctrl+G and Shift+Enter/Ctrl+Shift+G. Search-match highlight colors are customizable via new searchMatchBg and searchMatchText theme color tokens, with documented fallback behavior when omitted. Fullscreen mode also adds unbound single-line transcript scrolling actions.
Add search-match highlight colors to a custom theme; omit these tokens to use the built-in fallbacks.
json
"searchMatchBg": "#2d2d30",
"searchMatchText": ""
— Named keybindings and theme tokens, but no CLI commandv0.84.2
0500
Experimental strict JSON-schema constrained samplingnew78how completely this was documenteddepth25/40specificity25/30actionability28/3078 / 100
Under PI_EXPERIMENTAL=1, the default read, bash, edit, and write tools support experimental strict JSON-schema constrained sampling for schema-conformant outputs.
Enable strict JSON-schema constrained sampling for the built-in read/bash/edit/write tools to get schema-conformant outputs during experimentation.
$ PI_EXPERIMENTAL=1 pi interactive
Enable experimental strict JSON-schema constrained sampling for built-in tools to improve structured outputstructured outputForcing a model's response to match a given format or JSON schema, so software can parse it reliably instead of hoping the text is well formed. reliability.
$ PI_EXPERIMENTAL=1 pi
— Named env var and tools with runnable commandv0.84.2
0600
Configurable fullscreen exit outputnew68how completely this was documenteddepth28/40specificity22/30actionability18/3068 / 100
The fullscreenExitOutput config setting controls what prints when exiting fullscreen mode: "transcript" prints the final transcript and resume hint, while "resume-hint" restores the previous screen and prints only the resume hint; it has no effect in regular 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. mode.
— Exact config key and values, no example shownv0.84.2
thinner coverage below
0700
expandPromptTemplates option for sendUserMessagenew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
The extension pi.sendUserMessage() API gains an expandPromptTemplates option for explicitly dispatching commands and expanding skills and prompt templates.
Windows path syntax documented for JSON configimproved50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Docs now clarify that Windows paths in JSON config (e.g. shellPath) must use forward slashes (C:/Program Files/Git/bin/bash.exe) or escaped backslashes (C:\\Program Files\\Git\\bin\\bash.exe).
— Names exact config key and path formatsproduct docs
1100
AssistantMessage.endTurn field for Codex diagnosticsnew48how completely this was documenteddepth18/40specificity20/30actionability10/3048 / 100
A new AssistantMessage.endTurn field preserves OpenAI Codex's terminal end_turn signal for diagnostics.
— Named field, no example or mechanism detailv0.84.2
1200
AI_AGENT=pi process marker documentedimproved38how completely this was documenteddepth12/40specificity18/30actionability8/3038 / 100
Docs now document the AI_AGENT=pi process marker and how it differs from PI_CODING_AGENT=true.
Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.
Ollama added support for the new Qwen3.8 model family, including a 27B variant with an Apple Silicon 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. build, and refined how developer instructions from OpenAI-compatible coding agents are handled for Qwen3.8.
└──▷ 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
Qwen3.8 27B model with MLX variantnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds the qwen3.8:27b model, with performance gains across coding, research, and long-horizon agentic tasks, runnable via ollama run qwen3.8:27b. Also adds a qwen3.8:27b-mlx variant optimized for maximum performance and output quality on Apple Silicon devices, runnable via ollama run qwen3.8:27b-mlx.
Run the Qwen3.8 27B MLX variant on Apple Silicon for high-quality coding agent workloads.
$ ollama run qwen3.8:27b-mlx
— Names exact model tags and runnable commands.v0.32.12
thinner coverage below
0200
Qwen3.8 developer-instruction foldingimproved45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
Adds Qwen3.8 support for developer instructions: leading system/developer instruction prefixes sent by OpenAI-compatible coding agents are folded into a single system turn before Qwen3.8 validation, preserving instruction precedence without affecting Qwen3.5 or other renderers.
— Explains mechanism but gives no command or config to try.v0.32.13
OpenShell is the safe, private runtime for autonomous AI agents.
OpenShell v0.0.106 ships official Go and TypeScript SDKs and adds cert-manager and OpenShift Route support to its Helm chart deployment.
└──▷ 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
cert-manager and OpenShift Route support in Helm chartnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The Helm chart deployment adds cert-manager external issuer integration and OpenShift passthrough Route support.
— Names the integrations but no config keys or flags givenv0.0.106
0200
Go SDK for OpenShellnew35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
A complete Go SDK is now available, including domain clients, authentication, and hardening support.
— Names components but no install path or repo linkv0.0.106
0300
TypeScript SDK published as @nvidia/openshell-sdknew35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
A TypeScript SDK is now published as @nvidia/openshell-sdk.
— Names the exact package but no usage detailv0.0.106
ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.
ToolHive v0.43.0 adds plugin lifecycle tracking to lock files, OAuth confidential client and RFC 8693RFC 8693An IETF standard defining the OAuth 2.0 Token Exchange flow, letting a service swap one token for another with different scopes, audience, or type — enabling delegation and impersonation without re-authenticating the user. delegate client support, and makes push signing the default while removing the lock feature's opt-in gate, alongside smaller improvements to certificate 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. enforcement, rate-limiting observability, SSESSEServer-Sent Events, a browser API and HTTP-based protocol where a server pushes a stream of text events to a client over a single long-lived connection, giving tools a lightweight alternative to WebSockets for one-way real-time updates. parsing, and 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. tooling.
└──▷ WHAT SHIPPED ·
9 FEATURES1 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
Plugin lifecycle tracking in lock filesnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
The lock file schema now includes a plugins key so plugin entries are tracked in lock provenance, backed by a new PluginLockService and a managed install flag for plugin lifecycle management.
— Names schema key and service but no usage example givenv0.43.0
thinner coverage below
0200
Build fingerprint removed from proxy health endpointimproved55how completely this was documenteddepth15/40specificity25/30actionability15/3055 / 100
Drops the build fingerprint from the proxy /health response to reduce information exposure.
— Names exact endpoint but lacks further detailv0.43.0
0300
LLM config lifecycle and token helper commandimproved55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Resets the LLM config automatically when the last tool is torn down, and uses a bare thv command as the LLM token helper.
— Names the `thv` command but no flags or examplev0.43.0
0400
Confidential clients and RFC 8693 delegate clients in OAuthnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
ToolHive now supports confidential clients in dynamic client registration for OAuth flows, and makes RFC 8693 delegate clients reachable and usable for token-exchange workflows.
— Names standards involved but no endpoint or flag givenv0.43.0
0500
Certificate provenance enforcement in lock verificationimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Lock provenance now records the certificate ref and runner used for a build, and these values are enforced during skill verification.
— Describes mechanism but no config key or flag namedv0.43.0
0601
Default push signing and lock feature GAbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Pushes are now signed by default, and the lock feature's feature gate has been removed — it previously required explicit opt-in.
— States behavior change but no migration guidancev0.43.0
0700
Rate-limiting observability via OpenTelemetrynew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds rate-limiting observability through metrics and tracing using OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor..
— Names OpenTelemetry but no metric names or setup stepsv0.43.0
0800
Multi-line Modern SSE event parsingimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Parses multi-line Modern SSE events, broadening SSE protocol compatibility.
— Names protocol feature but no config or examplev0.43.0
0900
Trust state display in CLInew20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
Displays recorded trust state to the user in the CLI.
— Bare description with no command or flag namedv0.43.0
Cloudflare is a global network platform providing CDN, DDoS protection, DNS, security, and developer services for websites and applications.
Cloudflare shipped new DeepSeek V4 reasoning models in Workers AI, a full set of Worker-level Access controls (runtime identity context, local dev simulation, per-Worker policy attachment, and an account-wide default-protect mode), plus package-registry-aware Gateway policies, new Realtime SFUSFUA Selective Forwarding Unit: a media server architecture that relays incoming WebRTC streams to other participants without decoding them, reducing server CPU cost and latency in multi-party video or data pipelines. DataChannel reliability options, data-residency controls for Artifacts, FIDO2FIDO2The open standard behind passkeys and hardware security keys, where a website checks a signature from the user's device instead of a password. Because the key is bound to the site, phishing pages cannot use it.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. for infrastructure apps, GA Certificate TransparencyCertificate TransparencyA public, append-only log system maintained by various operators (Google runs several) that records every TLS certificate issued, letting anyone audit CAs for misissued or rogue certificates. Monitoring, and regex-based blocked-content rules in Email Security.
└──▷ WHAT SHIPPED ·
11 FEATURES0 OF 11 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
Jurisdiction field for Artifacts namespacesnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds a jurisdiction field to the Artifacts namespace API (POST /api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/artifacts/namespaces), supporting eu and us values for data localization; jurisdictions are immutable after namespace creation.
Configure an Artifacts namespace restricted to EU data residency at creation time.
Local Access simulation in wrangler.jsoncnew88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
Adds an access block inside the dev section of wrangler.jsonc to simulate Cloudflare Access identities locally — set aud, email, and related fields to test Access-gated Worker handlers without deploying; remove the block to simulate unauthenticated requests.
Test Cloudflare Access-gated Worker handlers locally with a simulated authenticated identity, without deploying.
Reliability fields in Realtime SFU DataChannels APInew85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds ordered, maxRetransmits, and maxPacketLifeTime fields to the Realtime SFU DataChannels API (POST /v1/apps/$APP_ID/sessions/$SESSION_ID/datachannels/new), enabling unordered and partially-reliable delivery modes.
DeepSeek V4 models in Workers AInew80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Adds @cf/deepseek-ai/deepseek-v4-pro-0813 and @cf/deepseek-ai/deepseek-v4-flash-0731 to Workers AI, both with a full 1,048,576-token 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., thinking-mode reasoning, and function callingfunction callingA model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions.; requires a Workers Paid plan or prepaid credits.
Package registry selectors in Gateway HTTP policiesnew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds pkg.ecosystem, pkg.name, pkg.version, pkg.namespace, and pkg.purl selectors to Cloudflare Gateway HTTP policies, enabling allow/block rules on software package downloads across npm, PyPI, RubyGems, Cargo, Go, Maven, and NuGetNuGetMicrosoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code.; requires TLS decryption.
Access identity in Worker request contextnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds ctx.access and ctx.access.getIdentity() to the Worker request context so authenticated requests expose the user's email, name, and groups without manual 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. validation.
Worker-level Access policy attachmentnew65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Enables attaching an Access policy to a Worker itself, rather than to individual routes or domains, so all associated domains, Custom Domains, workers.dev URLs, and preview URLs are covered automatically. An Access tab in the Workers & Pages dashboard lets admins view and manage these Worker-level Access policies.
Blocked content rules in Email Securitynew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds a Blocked content area under Policies & rules in Cloudflare Email Security, allowing administrators to define plaintext or regex rules scoped to message subject, body, or both; available on Enterprise and Enterprise + PhishGuard plans.
Global protect-all-Workers default modenew55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds a global 'protect all Workers by default' mode that requires an Access policy for every Worker account-wide, with per-Worker bypass exemptions to make specific Workers publicly accessible.
FIDO2 MFA for infrastructure appsnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds ssh_fido2_key and piv_key as supported MFA methods in application-level and policy-level settings for infrastructure applications via independent FIDO2 MFA.
Certificate Transparency Monitoring reaches GAimproved40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Promotes Certificate Transparency Monitoring to general availability across all Cloudflare plans, with automatic filtering of Cloudflare-issued certificate alerts and structured alert emails.