The Cyber Toolchain — issue 137, November 12, 2026
THE CYBER TOOLCHAIN
NO. 137
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED NOVEMBER 12, 2026 · EVERY DAY
EDITIONStail|grep|head|ls|diff|uniq
The daily firehose — everything the toolchain shipped today, already filtered.
We read every release from the 1325 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.
What stands out across today's releases, grouped by what it lets you do. Every tool named links to its entry below.
protect
Find the agent config files your developers already committed — and block the next one
GitLab pairs search APIs and scheduled historic secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. to surface .claude/settings.local.json files already in history with prohibited-filename push rules and group-wide .gitignore templates so they stop arriving; Duo Agentic Chat drives the cleanup. Semgrep's observe-only mode lets Guardian run against a repo set and show what it would have blocked before anyone's push starts failing — the usual reason rollouts stall.
Decide which agents and MCP servers are allowed to act on a user's behalf
Varonis's MCP GatewayMCP GatewayA server that sits between MCP clients and one or more Model Context Protocol backends, routing tool calls and aggregating context sources so a single endpoint exposes many AI-agent integrations at once. gives one place to allow or deny tools, APIs, agents 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. servers acting under a user's identity — today most teams have no inventory of what their developers wired up, let alone a switch. WitnessAI's guardrail REST endpoints wrap model and agent calls with runtime policy checks and add a discovery catalog of AI apps in use, with an agentless network-level option for estates where you cannot instrument every caller.
Query Sentinel's cheap lake tier interactively instead of waiting on a job
Interactive KQLKQLKusto Query Language, Microsoft's read-only query language for Azure Data Explorer and Microsoft Sentinel, used by cyber tools to filter, aggregate, and correlate large volumes of log and telemetry data at speed. over lake tables means hunting across long-retention data no longer requires exporting it or standing up a separate analytics path, and Fabric federation pulls external datasets into the same query. Hunts that previously stopped at the hot-tier retention boundary can now run against the full window.
Give agent processes a network exit you can audit and revoke
minimal's Box Egress Proxy issues certificates and keeps a hash-chained audit trail of what an agent box reached, with per-run network and egress flags — so a coding agent's outbound traffic becomes a reviewable record rather than an unknown. Docker Sandboxes adds Docker Hardened Image selection and tunable stalled-connection timeouts so a dropped VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. recovers instead of hanging the run.
Three unrelated things stand out today: GitLab can find and block leaked Claude Code settings across an instance; WitnessAI can enforce policy around live model and agent calls; tcpflow can start privileged captures without leaving root-owned evidence behind.
protect
Find and stop leaked Claude Code local settings before they spread
GitLab combined instance-wide discovery, historic scanning, push-time filename controls, shared ignore templates, and assisted cleanup for .claude/settings.local.json. Teams get a path to remove existing leaks and prevent new commits without stitching together search jobs, hooks, and one-off repo fixes.
Put runtime policy checks around AI agents and model calls
WitnessAI added guardrail REST endpoints that bracket model and agent calls, while Varonis added a gateway for deciding which tools, APIs, agents, 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. servers may act for users. That moves AI-use control closer to execution time, instead of relying only on documentation or after-the-fact review.
Run privileged capture without keeping root-owned output
tcpflow can now start a capture with the privileges needed for packet access, then hand output-file ownership to an unprivileged user. That reduces the cleanup and permission juggling after incident collection, and avoids leaving routine analysis artifacts tied to root.
minimal added the Box Egress Proxy, a certificate-issuing egress gatekeeper with hash-chained audit records for agent boxes. Teams can make outbound access a controlled, inspectable path instead of giving each run broad network reach and reconstructing activity later.
reverse_ssh v2.9.0 adds TOMLTOMLA configuration file format designed to be minimal and readable, mapping unambiguously to a hash table; cyber tools use it as a structured alternative to YAML or INI for config files.-based server configuration and improves proxy compatibility by handling Negotiate-only authentication challenges.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
SSH based reverse shell
reverse_ssh v2.9.0 adds TOMLTOMLA configuration file format designed to be minimal and readable, mapping unambiguously to a hash table; cyber tools use it as a structured alternative to YAML or INI for config files.-based server configuration and improves proxy compatibility by handling Negotiate-only authentication challenges.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
TOML configuration file supportnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
The RSSH server can now be configured via a TOML file by passing --config <path> instead of relying solely on CLI flags, enabling repeatable, version-controlled server deployments.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Start the RSSH server from a TOML config file instead of passing all options on the command line — useful for repeatable, version-controlled server deployments.
$ ./server --config /etc/rssh/server.toml
— Names exact flag and file format with runnable examplev2.9.0
thinner coverage below
0200
Negotiate-only proxy authentication handlingimproved40how completely this was documenteddepth15/40specificity20/30actionability5/3040 / 100
reverse_ssh now handles proxies that advertise Proxy-Authenticate: NegotiateProxy-Authenticate: NegotiateAn HTTP response header a proxy sends to demand Kerberos or NTLM authentication via the GSSAPI Negotiate scheme, letting cyber tools integrate with enterprise single-sign-on infrastructure transparently. without also advertising NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent..
— Names exact header but no usage steps givenv2.9.0
Sippts 4.2.2 brings full SIP-over-WebSocketSIP-over-WebSocketA transport binding that carries SIP signaling messages inside WebSocket connections, letting browser-based VoIP clients speak SIP without needing raw TCP or UDP access. capability to its core commands and removes the standalone wssend module in favor of integrated WebSocket sending.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Sippts is a set of tools to audit SIP based VoIP Systems
Sippts 4.2.2 brings full SIP-over-WebSocketSIP-over-WebSocketA transport binding that carries SIP signaling messages inside WebSocket connections, letting browser-based VoIP clients speak SIP without needing raw TCP or UDP access. capability to its core commands and removes the standalone wssend module in favor of integrated WebSocket sending.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
SIP-over-WebSocket support across scan, enumerate and sendbreaking95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Sippts extends SIP-over-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. support across the scan, enumerate, and send commands: scan gains -p ws, -p wss, and an expanded -p all that now includes ports 5061/TLS, 8088/WS, and 8089/WSS, plus support for comma-separated transport lists like -p udp,tls,wss; a new -path flag enables automatic WebSocket path discovery in scan, enumerate, and send; enumerate adds -p ws|wss and -path for method enumeration over WebSocket; and the wssend module has been removed, with its functionality replaced by send -p ws and send -p wss.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ All WebSocket traffic is handled by a new shared client, lib/wsclient.py, implementing RFC 7118.
Enumerate supported SIP methods on a WebSocket endpoint when a standard UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery./TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. scan yields no results.
Flipper Zero Unleashed Firmware, an unlocked alternative firmware.
Unleashed Firmware's unlshd-095 release adds a Remote Analyzer app for detecting undecoded garage/gate remotes, a T5577T5577A reprogrammable RFID chip commonly used in 125 kHz proximity cards, widely supported by researchers because it can emulate many legacy card formats for access-control testing. app with password-sniffing, new SubGHzSubGHzRadio frequencies below 1 GHz (typically 300–900 MHz) used by IoT devices, key fobs, and industrial sensors; cyber tools target this band to capture, replay, or analyze those wireless signals. protocol decoding for several remote families, and expands Nice O-Code and Seed Capturer with RAW-file decoding, alongside a breaking renumbering of KeeLoqKeeLoqA proprietary block cipher developed by Microchip Technology, used in rolling-code systems for keyless entry devices; cyber tools target it to analyze or attack RF-based access control protocols. CounterMode values.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
New SubGHz remote protocols and custom buttonsnew75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Adds decoding and replay support for KeeLoq Phantom/Hiland (now reads and sends properly, available as KL: Phantom/Hiland 433M in Add Manually, with CounterMode: 10 sending the resync pair 0xFFFE then 0xFFFF in one press as a clone remote), FAAC TM 12 dip-switch TM 433/868 DS remotes (available as FAAC TM 433MHz and FAAC TM 868MHz in Add Manually), Nero Radio rolling remotes, Freezer remotes, and Proteco MOVER remotes with custom buttons; Dooya remotes also gain custom button support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Enumerates Add Manually entries and counter mode values across protocolsunlshd-095
0200
CLI infrared signal transmissionnew70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
Send infrared signals over the CLI with ir universal <remote> <signal> without rebooting the device.
Send a specific infrared signal from a universal remote database over the CLI without triggering a device reboot.
$ ir universal <remote> <signal>
— Exact runnable command with example, minimal mechanism detailunlshd-095
0300
Remote Analyzer appnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds the Remote Analyzer app, which detects garage and gate remotes that SubGHz does not yet decode and shows their type and details, detects Life Fido remotes and Crypt/Crypt Lite encrypted remotes, and includes Mod. sweep, which walks modulations one second at a time while a remote transmits and locks onto the one that works.
— Explains detection mechanism and sub-features, no exact commandunlshd-095
0400
T5577 app with password sniffingnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds a T5577 app that reads a T5577 tag, saves it to /ext/lfrfid, and writes it back, with Sniff Password to recover a tag password by listening to a reader or cloner write a tag and keep found passwords in a personal dictionary.
— Names file path and feature, lacks exact command invocationunlshd-095
0500
T5577 developer API exportsnew70how completely this was documenteddepth20/40specificity30/30actionability20/3070 / 100
Exports the T5577 block read/write API for apps via t5577.h and t5577_file.h, plus faac_slh_reset_prog_mode, subghz_protocol_decoder_base_get_type, ibutton_protocols_is_writable, and bit_lib_reverse_32_fast.
— Names exact headers and functions but no usage exampleunlshd-095
0600
Nice O-Code decoding and cloning upgradesimproved70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Nice O-Code app can now decode a saved RAW .sub file and shows the certificate beside the installer code, supports the longer 72-bit frame as Nice O-Code One 433MHz and 112-bit certificate frames as Nice O-Code+Crt 433MHz in Add Manually, and its New remote option mints a serial the gate is certain to enrol.
— Names frame types and Add Manually entries, no exact commandunlshd-095
thinner coverage below
0700
Seed Capturer RAW decoding and BFT Mitto supportnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Seed Capturer can decode a saved RAW .sub file and supports BFT Mitto remotes on 433.92 MHz using an external CC1101 module.
— Names frequency and hardware requirement, limited further detailunlshd-095
0801
KeeLoq CounterMode renumberingbreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
KeeLoq CounterMode: 7 now sends what CounterMode: 8 previously sent; the old CounterMode: 7 resync pack is now mode 8, and the previous mode 8 is now mode 9.
— States exact mode remapping but no migration stepsunlshd-095
0900
Half-rate KeeLoq decodingimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
KeeLoq remotes that send at half the usual rate (Te 200us) are now decoded and sent back at the rate they were received, shown as Crypt Key instead of an unknown manufacturer.
— Describes behavior change but no interaction stepsunlshd-095
└──▷ BREAKING ON UPGRADE
!
KeeLoq `CounterMode: 7` now sends what `CounterMode: 8` previously sent; the old `CounterMode: 7` resync pack is now mode 8, and the previous mode 8 is now mode 9.Our best guess
Get started with Semgrep to help you catch, flag, and fix real vulnerabilities before they ship.
Semgrep shipped a hosted MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server for editor and terminal access to findings, an observe-only mode for Guardian rollouts, and support for bringing your own AI provider keys to Agentic Workflows, alongside Supply Chain, language-parsing, and advisory-matching improvements — while dropping Intel Mac binaries after 1.182.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
12 FEATURES2 OF 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
semgrep ci exits with code 2 on dependency resolution failureimproved90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
With --allow-local-builds, running semgrep ci --no-suppress-errors now exits with code 2 when dependency resolution fails for a subproject, listing the affected dependency sources in scan output.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Hosted MCP server and workspace scanningnew88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
Semgrep adds a hosted MCP server in public beta, letting Claude Code, Codex, Cursor, VS Code, or any MCP client search and triage findings, run scans, and manage policies from the editor or terminal with permissions following your AppSecAppSecApplication security: the practice of finding and fixing vulnerabilities in software during design, development, and testing. Cyber tools build on AppSec workflows to shift vulnerability detection earlier in the development lifecycle. Platform role. The semgrep mcp server can now scan files outside the MCP client's workspace root by setting SEMGREP_MCP_ALLOW_SCAN_OUTSIDE_WORKSPACE=true.
Let the Semgrep MCP server scan files that live outside the MCP client's workspace root, such as shared library directories.
Guardian observe-only modenew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Semgrep Guardian adds an observe-only mode, enabled by setting SEMGREP_GUARDIAN_OBSERVE_ONLY=1, which lets Guardian scan as usual while hiding results from developers and coding agents until you're ready to roll it out.
Shadow-deploy Guardian to see what it finds before surfacing results to developers or coding agents.
Bring-your-own AI provider keys for Agentic Workflowsnew78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Agentic Workflows can now run on your own AI provider keys for OpenAI, Anthropic, Google Gemini, xAI, and Microsoft Foundry, so configured model requests and AI-powered detection use your providers instead of Semgrep-managed keys. Microsoft Foundry (formerly Azure OpenAI) now has its own card in AI provider settings, accepting a resource endpoint, an API key, and one or more deployments each with its model.
— Names providers and config fields, no exact commandsnapshot-20261112
0502
Dropped Intel Mac CLI binariesbreaking75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
The Semgrep CLI no longer ships binaries for Intel Macs; version 1.182 is the last release supporting them. Use the semgrep/semgrep Docker image on Intel Mac or native arm64 Python on Apple silicon.
Expanded language syntax parsingimproved68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Semgrep Code now parses newer Bash arithmetic expressions such as $(( $X * 2 )), Clojure files using reader-evaluated metadata (^#=(...)) or the legacy #^ prefix, and Swift 5.9 syntax including macros, parameter packs, and if and switch expressions.
Advisory version-range matches and Slack alertsnew62how completely this was documenteddepth25/40specificity22/30actionability15/3062 / 100
An advisory's matching projects now include a 'Potentially matching: declared in a version range' section listing each project, branch, file, and declared version. Incident Slack notifications also report how many such projects exist and which packages they declare.
The Semgrep CLI no longer ships binaries for Intel Macs; version 1.182 is the last release supporting them. Use the `semgrep/semgrep` Docker image on Intel Mac or native arm64 Python on Apple silicon.Our best guess
Syzkaller is an unsupervised coverage-guided kernel fuzzer developed by Google that automatically finds bugs in OS kernels by generating and executing random syscall sequences.
syzkaller adds vhost/vsock executor helpers and support for disabling the #syz test command per reporting stage︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds syz_vhost_vsock_setup and syz_vhost_vsock_send executor helpers for fuzzing vhost vsock interfaces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports disabling the #syz test command per reporting stage via DisableTestCommandConfig with a custom message in dashboard and syz-cluster.
Adds ext4, fscrypt, and fsverity scenario seeds to sys/linux/test for improved kernel fuzzing coverage.
Improves ext4, quota, fscrypt, and fsverity syscall descriptions in sys/linux.
Updates pkg/aflow backend to use the gemini-4-carbon model for deep reasoning.
Adds syz_vhost_vsock_setup and syz_vhost_vsock_send executor helpers for fuzzing vhost vsock interfaces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports disabling the #syz test command per reporting stage via DisableTestCommandConfig with a custom message in dashboard and syz-cluster.
GitHub brought issue types and issue fields to personal-account repositories, complete with REST/GraphQL and webhook support, and let users create labels and milestones directly from an issue.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
GitHub is a web-based platform for version control and collaborative software development using Git repositories.
GitHub brought issue types and issue fields to personal-account repositories, complete with REST/GraphQL and webhook support, and let users create labels and milestones directly from an issue.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Issue types and fields for personal accountsnew88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
GitHub now supports issue types and issue fields on personal-account repositories, manageable via the REST and GraphQL APIs and webhooks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Up to 25 issue types can be customized from the Issue types page under Planning in account settings (defaults: Bug, Task, Feature), and up to 25 issue fields from the Issue fields page under Planning (defaults: Priority, Effort, Start date, Target date), supporting text, number, date, single-select, and multi-select field types. Issue fields can be pinned to specific issue types or left available on issues without a type, and both types and fields can be used in projects to create custom views and perform bulk updates.
Create a new issue type for a personal-account repository to standardize triage across your open-source projects.
📍In your personal account settings, go to Planning › Issue types, then click New issue type and define a name, description, and color.
Create a custom single-select Priority field and pin it to the Bug issue type so it always appears when filing bugs.
📍In your personal account settings, go to Planning › Issue fields, click New issue field, choose Single-select, name it Priority, add options (Critical, High, Low), then pin it to the Bug issue type.
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
Terraform v1.17.2 improves performance of the query command for large-scale configuration generation from HCP Terraform.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Faster, lower-memory query configuration generationimproved45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
The query command now uses less memory and runs faster when generating configuration from large HCP Terraform queries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the command but no metrics or mechanism.v1.17.2
OpenQodex is a join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.
OpenQodex 0.18.0 adds support for Goose as a coding agent, automating its setup via a new init flag.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Goose agent support via init flagnew88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
Running openqodex init --agent goose sets up Goose as a coding agent: it adds a review hint to Goose's hints file and an openqodex skill to Goose's folders.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The command locates Goose via ~/.config/goose or via XDG_CONFIG_HOME when that environment variable is set.
Register OpenQodex with Goose so it adds a review hint and skill automatically, using either the default config location or a custom XDGXDGA set of specifications maintained by freedesktop.org that standardise where Linux applications store config, data, and cache files, letting tools respect user-defined paths instead of hardcoding locations. path.
Teams and agents ship trusted software faster with GitLab, the intelligent orchestration platform with context and governance for the entire software lifecycle.
GitLab shipped a full toolkit for finding and eliminating leaked Claude Code .claude/settings.local.json files across an instance, combining new search APIs, Secret Push Protection rollout guidance, scheduled historic secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it., group-wide .gitignore templates, prohibited-filename push rules, and Duo Agentic Chat-driven cleanup.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES6 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
API endpoints to discover leaked Claude Code settings filesnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
New API calls for locating .claude/settings.local.json across an instance: GET /api/v4/groups/<id>/search?scope=blobs&search=filename:settings.local.json%20path:.claude&exclude_forks=false&per_page=100 finds all current copies across a group, GET /api/v4/search?scope=blobs&search=filename:settings.local.json%20path:.claude searches an entire self-managed instance without looping over groups, GET /api/v4/groups?owned=true&top_level_only=true&per_page=100 lists every top-level group you own for bulk scanning, and GET /api/v4/projects/<id>/forks lists all forks of an affected project so their independent histories are also checked.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Check whether .claude/settings.local.json ever appeared in a project's full commit history — catches deleted files and all branches, not just the current default branch.
Scheduled historic secret detection via scan execution policynew85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Run GitLab Secret Detection across every project in a group, including those with no .gitlab-ci.yml, by creating a scan execution policy under Group > Secure > Policies > New policy > Scan execution policy with a weekly-schedule rule and the variable SECRET_DETECTION_HISTORIC_SCAN: 'true' to cover full commit history.
Prohibited filename push rule for Claude Code settings filenew75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Enforce a prohibited filename rule across a group via Settings > Repository > Pre-defined push rules with the pattern (^|/)\.claude/settings\.local\.json$ under Prohibited filenames, blocking the file from ever being pushed.
Block .claude/settings.local.json from landing in any project — apply the push rule to every project in a group by looping over project IDs.
$ # Get all project IDs in the group
curl --header 'PRIVATE-TOKEN: <token>' \
'https://gitlab.com/api/v4/groups/<group_id>/projects?include_subgroups=true&per_page=100' \
| jq '.[].id'
# Apply the push rule to each project (use PUT if the project already has push rules)
curl --request POST \
--header 'PRIVATE-TOKEN: <token>' \
--header 'Content-Type: application/json' \
--data '{"file_name_regex": "(^|/)\\.claude/settings\\.local\\.json$"}' \
'https://gitlab.com/api/v4/projects/<id>/push_rule'
Secret Push Protection rollout for Self-Managednew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Enable Secret Push Protection on GitLab Self-Managed by turning it on under Admin > Settings > Security and compliance, then activating it per project under Secure > Security configuration > Secret push protection or via the group security settings API.
Group-wide .gitignore template inheritancenew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Inherit a .gitignore entry for .claude/settings.local.json in every new project by adding it to the group's file templates project under Settings > General > Templates.
Make every new project in a group inherit a .gitignore rule that excludes .claude/settings.local.json, so the gap Claude Code leaves is closed by default.
📍In the group, go to Settings › General › Templates, select your file templates project, and add a .gitignore that includes the line:
.claude/settings.local.json
Duo Agentic Chat group-wide audit and cleanupnew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Use GitLab Duo Agentic Chat in a top-level group to audit all projects for the Claude Code settings file — including deleted copies and non-default branches — and to open merge requests that remove the file and add it to .gitignore across the whole group in two approval clicks.
fcaptcha shipped an official React integration package and a new paired-observation analyzer for detecting automated agents in browser captures.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
fcaptcha shipped an official React integration package and a new paired-observation analyzer for detecting automated agents in browser captures.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Official React package for fcaptchanew75how completely this was documenteddepth25/40specificity22/30actionability28/3075 / 100
The @webdecoy/fcaptcha-react npm package integrates fcaptcha into React 18 and 19 applications, including SSRSSRServer-Side Rendering: a web architecture pattern where HTML is generated on the server per request rather than in the browser, giving frameworks faster initial page loads and better crawlability. and StrictMode environments.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It rejects conflicting page-wide serverUrl configuration instead of silently redirecting widgets to the wrong server, and ships TypeScript declarations along with explicit backend token-verification guidance.
Add fcaptcha to a React 18 or 19 project, including SSR setups where a bare script tag would fail.
$ npm install @webdecoy/fcaptcha-react
— Named package, install command, and specific safeguards described.v1.49.0
thinner coverage below
0200
Paired-observation analyzer for agent detectionnew43how completely this was documenteddepth20/40specificity15/30actionability8/3043 / 100
A new paired-observation analyzer screens candidates against every captured human using consistent-direction and leave-one-pair-out checks, aimed at browser-internal agent/control captures.
— Mechanism named but no interface or usage detail given.v1.48.2
Kingfisher is a detect secrets. Validate them live.
Kingfisher adds live finding counts during CLI scans, a Node SDK showcase (Kingfisher Workbench), and new Node SDK APIs for dependency-aware rule loading and scoped validation.
└──▷ GET THIS VERSIONHomebrewDockerpipxgit
Homebrew
$ brew install kingfisher
# already installed? upgrade to this version:$ brew upgrade kingfisher
Docker
$ docker pull ghcr.io/mongodb/kingfisher:2.18.1
pipx
$ pipx install kingfisher-bin==2.18.1
# already installed? upgrade to this version:$ pipx install --force kingfisher-bin==2.18.1
git
$ git clone --branch v2.18.1 https://github.com/mongodb/kingfisher.git
# already have the repo? check out this version:$ git checkout v2.18.1
Homebrew lists this version · published under the project's GitHub account · PyPI attestation · checked 12 Nov
Show live reportable finding counts on stderr during CLI scanning and validation without affecting final report deduplication; progress stays on interactive stderr only.
Adds Kingfisher Workbench, a Node SDK showcase at javascript/examples/kingfisher-workbench/ with working-tree and Git-history scans, live progress, redacted HTML reports, synthetic screenshots, and a loopback validation/revocation demo.
New vulnerability checkAdds opt-in Rules.load({ includeDependencies: true }) on the Node SDK to retain transitive helper rules below the requested confidence before compilation.
Adds Validator.validate(findings, { candidates }) on the Node SDK to scope provider checks without discarding the original helper batch; candidates are preflighted like RevocationPlan.validate() and incomplete inputs are skipped before any provider request.
Adds non-copying ScanInput.byteLength to the Node SDK.
5 details in Everything
└──▷ BREAKING ON UPGRADE
!
Dynamic confidence upgrades and demotions are removed across the CLI and SDKs; each rule now uses its configured confidence. Legacy custom YAML/TOML confidence helpers are inert.Our best guess
An explicitly selected rule whose confidence is below the active threshold now errors before compilation, including when used alongside `--rule all`; previously it would run silently.Our best guess
Finite State Platform shipped an estimated-count header for Audit Trail pagination, a new endpoint to poll for pending finding recalculations after component status changes, time-windowed CVE update queries, BrotliBrotliA lossless compression algorithm developed by Google that typically achieves better ratios than gzip at comparable speeds, making it attractive for reducing payload sizes in network-facing tools. component detection with version reading in binary scans, and corrected vendor/OS naming for Debian and Ubuntu packages in vulnerability results.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Finite State Platform is a software supply chain security tool that analyzes firmware and embedded software for vulnerabilities, risks, and compliance issues.
Finite State Platform shipped an estimated-count header for Audit Trail pagination, a new endpoint to poll for pending finding recalculations after component status changes, time-windowed CVE update queries, BrotliBrotliA lossless compression algorithm developed by Google that typically achieves better ratios than gzip at comparable speeds, making it attractive for reducing payload sizes in network-facing tools. component detection with version reading in binary scans, and corrected vendor/OS naming for Debian and Ubuntu packages in vulnerability results.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Pending finding-update polling endpointnew85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
A GET /public/v0/components/finding-updates/{projectVersionId} endpoint reports which components still have findings being recalculated, surfaced via the X-Finding-Updates-Pending header, so automation can poll after a PUT /public/v0/components/{projectVersionId}/{componentId}/status status change (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ marking a component false_positive) before acting on results.
Poll whether a large component's findings have finished updating after marking it False Positive, so downstream automation does not act on stale data.
Audit Trail API total count estimationimproved78how completely this was documenteddepth25/40specificity28/30actionability25/3078 / 100
Audit Trail API endpoints now set the X-Total-Count-Estimated: true response header when the total exceeds 10,000 events, letting clients detect when the reported count is approximate before relying on it for a full paginated export.
Check whether the Audit Trail total is an estimate before deciding to export a CSV for the full record, avoiding pagination gaps above 10,000 events.
CVE update events endpoint with time filtersimproved70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
The GET /public/v0/cves/updates endpoint accepts start and end timestamp parameters to pull CVE update events for a given window, and returns a validated error response when an unsupported filter field is supplied.
Pull CVE update events for a wide time window and handle the validated error response when an unsupported filter field is supplied.
Debian and Ubuntu package naming in vulnerability resultsimproved41how completely this was documenteddepth18/40specificity15/30actionability8/3041 / 100
Vulnerability results now include Debian and Ubuntu packages that previously appeared with no vendor and no operating-system component named.
Ipatool is a command-line tool that allows you to search for iOS, iPadOS, tvOS, watchOS, visionOS, and macOS apps on the App Store, and download .ipa or macOS .pkg app packages.
ipatool restores broken App Store authentication with local Anisette generation, speeds up downloads with parallel streams, and expands compatibility to cover delisted apps, legacy iOS packages, and more App Store regions.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES2 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Local Anisette generation for App Store authenticationimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
App Store authentication now works again via local Anisette generation and provisioning, removing the dependency on external Anisette servers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Store operations and signing now use the modern Apple protocol, improving compatibility with current App Store requirements.
— Explains mechanism and cause but no config/flag namesv2.8.0
0200
Dynamic App Store storefront discoveryimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
ipatool now discovers App Store storefronts dynamically, supporting regions not in the built-in list.
— Clear behaviour change but no concrete region listv2.8.1
0300
Actionable auth error dialogsimproved40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
ipatool now shows Apple's authentication dialogs and account-action links when sign-in fails, making auth errors actionable.
— Describes user-facing behaviour, no exact UI/flag detailv2.8.1
0400
Parallel download streams for large appsimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
ipatool now downloads large app packages using parallel download streams for faster transfers.
— Describes benefit, no mechanism or flag detailv2.8.1
0502
Download support for delisted and legacy appsnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
ipatool now recovers previously acquired, delisted iOS apps, and supports downloads of legacy iOS apps that lack platform declarations.
— Two thin compatibility fixes grouped, no mechanism givenv2.8.0v2.8.1
edb-debugger 1.6.0 ships a hardware breakpoint dialog, breakpoint-aware and library-load-aware bookmark handling, cancelable dialog searches, automatic function block comments, Qt6 build support, and a UI layout reset option.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
edb is a cross-platform AArch32/x86/x86-64 debugger.
edb-debugger 1.6.0 ships a hardware breakpoint dialog, breakpoint-aware and library-load-aware bookmark handling, cancelable dialog searches, automatic function block comments, Qt6 build support, and a UI layout reset option.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Hardware breakpoint configuration dialognew55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
edb adds a hardware breakpoint dialog for configuring hardware breakpoints through the UI, accessed from the debugger menu to select address, condition (execute, read, write), and width.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
When you need to trigger on memory access or execution without consuming a software breakpoint slot, open the hardware breakpoint dialog from the debug menu to configure a hardware breakpoint.
📍In the debugger menu, open the hardware breakpoint dialog, select the address, condition (execute, read, write), and width, then apply.
— Names the dialog and configurable options with UI steps.1.6.0
0200
Bookmark save/restore with library load awarenessnew52how completely this was documenteddepth25/40specificity12/30actionability15/3052 / 100
Bookmarks now persist correctly across sessions that involve dynamic library loading, so analysis positions set via the Bookmarks panel survive restarts even when library base addresses shift.
When debugging a binary that uses dynamic libraries, use bookmark save/restore to keep your analysis positions intact across restarts where library base addresses may shift.
📍In the Bookmarks panel, set your bookmarks as usual; they are automatically saved and restored with library load awareness on the next session.
— Explains persistence mechanism and when it applies, with usage steps.1.6.0
0300
Qt6 build supportimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
edb-debugger now supports building and running with Qt6, including Qt 6.11.
— Names specific Qt version but no build steps given.1.6.0
0400
Automatic function block commentsnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
edb adds automatic function block comments before detected functions in the disassembly view.
— Names the feature and view, but no mechanism detail.1.6.0
0500
Cancelable search dialogsimproved25how completely this was documenteddepth15/40specificity5/30actionability5/3025 / 100
edb adds cancelable search in most or all dialogs, allowing long-running searches to be interrupted.
— States behaviour but no specific dialogs or commands named.1.6.0
0600
Reset UI layout from GUInew25how completely this was documenteddepth10/40specificity5/30actionability10/3025 / 100
edb adds the ability to reset the UI layout from within the GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands..
— Minimal description; no menu path or config detail given.1.6.0
0700
Bookmark breakpoint indicatornew20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
edb now shows which bookmarks have breakpoints set, making it easier to distinguish breakpoint-annotated bookmarks at a glance.
— Bare description of a visual indicator, no mechanism detail.1.6.0
Netcap's v0.16.5 release reworked the analyst web UI's chart handling and the /api/chart/data endpoint, redesigned the offline rule evaluation flow into three distinct steps, and overhauled the connections and services views.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Netcap is a framework for secure and scalable network traffic analysis - https://netcap.io
Netcap's v0.16.5 release reworked the analyst web UI's chart handling and the /api/chart/data endpoint, redesigned the offline rule evaluation flow into three distinct steps, and overhauled the connections and services views.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Chart data endpoint response codesimproved90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
The /api/chart/data endpoint now answers 204 No Content when no plottable values exist in scope, and 200 with an empty series for format=json; read and configuration failures remain 500.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Exact endpoint path, query param and status codes givenv0.16.5
0200
Dashboard chart display and layout improvementsimproved65how completely this was documenteddepth28/40specificity25/30actionability12/3065 / 100
Categorical charts now show the 20 most frequent values, with ties broken by name for a deterministic cut-off. Dashboard charts with no data in the selected scope are now hidden and the grid closes the gap automatically, and the dashboard grid now follows its container width, keeps rows aligned, stacks below 768 px, and scrolls pie legends while truncating axis labels.
— Named thresholds but UI-only behavior, no API or commandv0.16.5
0300
Three-step offline rule evaluation flowimproved65how completely this was documenteddepth28/40specificity22/30actionability15/3065 / 100
Offline rule evaluation now presents pack, validation and evaluation as three distinct steps with status, readable limit units, and a results summary of alerts, records, matched rules and elapsed time.
— Describes flow structure but no exact UI path givenv0.16.5
thinner coverage below
0400
Connections and services view redesignimproved50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
Connections and services views now collapse behavioral context by default and display observations as a table, with directional byte bars and an aligned packet table replacing stacked statistics.
— Describes layout change but no navigation path or metric namesv0.16.5
Microsoft Sentinel added interactive KQLKQLKusto Query Language, Microsoft's read-only query language for Azure Data Explorer and Microsoft Sentinel, used by cyber tools to filter, aggregate, and correlate large volumes of log and telemetry data at speed. lake queries over Sentinel tables and federated external data via Microsoft FabricMicrosoft FabricA Microsoft cloud analytics platform that unifies data engineering, warehousing, and business intelligence under one SaaS service, giving cyber tools a single place to ingest, store, and query large volumes of telemetry..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Microsoft Sentinel is a find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.
Microsoft Sentinel added interactive KQLKQLKusto Query Language, Microsoft's read-only query language for Azure Data Explorer and Microsoft Sentinel, used by cyber tools to filter, aggregate, and correlate large volumes of log and telemetry data at speed. lake queries over Sentinel tables and federated external data via Microsoft FabricMicrosoft FabricA Microsoft cloud analytics platform that unifies data engineering, warehousing, and business intelligence under one SaaS service, giving cyber tools a single place to ingest, store, and query large volumes of telemetry..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Interactive KQL lake queries via Microsoft Fabricnew63how completely this was documenteddepth25/40specificity18/30actionability20/3063 / 100
Users can run interactive KQL lake queries on Microsoft Sentinel tables and federated external data sources using Microsoft Fabric, enabling custom analytics on data lake tables and external data tables.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ In practice, this means opening a KQL queryset in Microsoft Fabric, connecting to a Microsoft Sentinel workspace, and running a lake query across Sentinel tables or external federated data sources.
Query Sentinel tables and federated external data sources interactively via Microsoft Fabric when you need ad-hoc analytics beyond standard Sentinel workbooks.
📍In Microsoft Fabric, open a KQL queryset, connect to your Microsoft Sentinel workspace, and run a lake query across Sentinel tables or external federated data sources.
Databricks is a unified data analytics platform that enables collaborative data engineering, machine learning, and analytics using Apache Spark in the cloud.
Databricks shipped a mix of AI-assistant integrations and platform extensions this window, headlined by bring-your-own ChatGPT billing through Unity Gateway, Python-based custom service policies in Unity Catalog, and new Genie One client surfaces for Windows and Chrome.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES3 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Text and binary inputs for protobuf model serving requestsnew80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Custom model serving endpoints (Public Preview) now accept text and binary data — titles, images, audio, and documents — as KServe v2KServe v2An open inference protocol (maintained by the KServe community) that standardises how clients send prediction requests to ML model servers, letting cyber tools swap backends without changing their inference code.BYTES tensorsBYTES tensorsTensors whose elements are raw byte values rather than numeric types, used in ML frameworks to handle arbitrary binary data or variable-length strings without numeric interpretation. alongside numeric tensors in the same protobuf request, with binary model outputs also returned as BYTES tensors.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Genie One Chrome extension (Beta)new75how completely this was documenteddepth25/40specificity20/30actionability30/3075 / 100
Install the Genie One Chrome extension from the Chrome Web Store to open your Databricks workspace in every new Chrome tab, giving one-click access to asking questions, searching across tools, and opening dashboards.
Set Genie One as your Chrome new tab page so every tab opens directly into your Databricks workspace for instant querying and dashboard access.
📍1. Go to the Chrome Web Store and search for Genie One.
2. Click Add to Chrome to install the extension.
3. Open a new Chrome tab — it now loads Genie One in your Databricks workspace.
Custom service policies in Python for Unity Catalog (Beta)new70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Write custom service policies as Python functions in Unity Catalog to express rules that SQL cannot handle, such as regular expressions, Python packages, or calls to an external guardrail through a service credential.
ChatGPT and Claude as partner platforms in ingress policiesNew integrationnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Context-based ingress policies now support ChatGPT and Claude as partner platforms, letting hosted MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. clients — such as the Databricks Genie plugins for ChatGPT and Claude — reach your workspace without manually tracking their IP ranges.
Bring your own ChatGPT subscription to Codex via Unity Gatewaynew60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Connect your own ChatGPT Go, Plus, Pro, or Enterprise subscription to Codex and the ChatGPT desktop app through Unity Gateway, with requests billed to your subscription and access governed by Unity Gateway.
Genie One desktop app for Windows (Beta)new45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
The Genie One native desktop app now supports Windows (Beta), letting users chat with data in natural language, manage threads and documents, and use Genie Agents outside a browser.
Databricks adds a Genie plugin that connects ChatGPT to the Genie One 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. for natural-language data queries.
Tines is an apps, agents and automations, in the complete environment for enterprise AI.
Tines 44.3.0 improves visibility across cases, scheduled actions and credentials, adding webhook case tracking, credential-refresh alerts, and new notification and dashboard controls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Custom date filter on dashboardsnew37how completely this was documenteddepth15/40specificity10/30actionability12/3037 / 100
Tines now lets users apply their own date filter on dashboards for custom time-range exploration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
ClamUI v0.6.0 preserves full scan evidence past the 64 MiB output limit, adds a protected stdin transport for very long daemon paths, adds Vietnamese localization, and improves history/quarantine browsing plus VirusTotal upload security checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Clamui is a clamav Desktop application ( GUI )
ClamUI v0.6.0 preserves full scan evidence past the 64 MiB output limit, adds a protected stdin transport for very long daemon paths, adds Vietnamese localization, and improves history/quarantine browsing plus VirusTotal upload security checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Protected stdin transport for long daemon pathsimproved70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Daemon paths of 1,023 bytes or more now use the protected stdin transport instead of being split, retaining exclusions, progress, and cancellation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact byte threshold and the before/after transport change.v0.6.0
0200
Full scan evidence retention beyond 64 MiB limitimproved60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
ClamUI now retains findings, skipped files, warnings, and summary counts after the 64 MiB displayed-output limit for both ClamAV backends, so large-scan history and final results preserve evidence and exact filename identities.
— Explains mechanism and scope but no exact UI path or command.v0.6.0
thinner coverage below
0300
History and quarantine browsing improvementsimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
History loads through a recoverable metadata index, quarantine browsing uses bounded pages with Unicode-aware search, and progress updates are coalesced without dropping threat changes or terminal events.
— Describes mechanism but no concrete config or UI path.v0.6.0
0400
VirusTotal upload pathname substitution checkimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
VirusTotal uploads are now rejected if the original pathname is substituted after lookup, alongside the existing no-follow descriptor identity checks.
— Describes security check but no exact flag or config exposed.v0.6.0
0500
Vietnamese localization addednew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
ClamUI adds Vietnamese (vi) to its desktop and CLI translation catalogs.
— Names the locale code but gives no further mechanism.v0.6.0
Avast Business Hub made a small usability improvement to its device management reporting, adding reboot history to CSV exports.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Avast Business Hub is a layered IT protection platform that is easy to implement and manage, designed for SMBs that want the highest level of protection for their business.
Avast Business Hub made a small usability improvement to its device management reporting, adding reboot history to CSV exports.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Last reboot time in device CSV exportimproved50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Device list CSV exports now include a Last reboot time column, surfacing reboot history alongside existing device data.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact column added but no export path or limitsNovember 2026
Simplify IT with Patch My PC's endpoint management software. Automate patching, app updates, reporting, and analytics to save time and boost security.
Patch My PC's Publisher preview release adds remote visibility into sync logs and changes default installer return code handling across major deployment targets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Remote access to wsyncmgr.log in console sessionsnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Publisher now lets admins view wsyncmgr.log directly within remote console sessions, without needing a local Publisher session on the machine performing the sync.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Catalog-defined installer return codes as defaultimproved35how completely this was documenteddepth10/40specificity20/30actionability5/3035 / 100
Publisher now treats catalog-defined installer return codes as the default behavior for WSUSWSUSWindows Server Update Services, a Microsoft service that distributes Windows patches from a central server to managed endpoints, letting cyber tools audit, control, or abuse the patch pipeline across a Windows fleet., Configuration Manager, and Intune, per the release summary, though the exact mechanism of the change is not detailed in the available text.
Defectdojo is an open-source Unified Vulnerability Management, DevSecOps & ASPM
DefectDojo improved TruffleHog secret deduplication across commits and added automatic Jira ticket comment notifications via the Jira connector.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Stable TruffleHog secret IDs across commitsimproved55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
DefectDojo now assigns a stable unique_id_from_tool to each TruffleHog secret so that the same secret appearing in multiple commits is not duplicated as separate findings.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
oxo expanded its domain-name fingerprinting message vocabulary with new selectors covering web-archive, HTTP service, and DOMDOMThe browser's in-memory tree representation of a web page's structure, standardized by the W3C, giving cyber tools a programmable interface to read or manipulate page content at runtime.-based signals.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
oxo expanded its domain-name fingerprinting message vocabulary with new selectors covering web-archive, HTTP service, and DOMDOMThe browser's in-memory tree representation of a web page's structure, standardized by the W3C, giving cyber tools a programmable interface to read or manipulate page content at runtime.-based signals.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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 fingerprinting message types for domain namesnew55how completely this was documenteddepth15/40specificity25/30actionability15/3055 / 100
oxo added new message/selector types for domain-name asset fingerprinting: v3.fingerprint.domain_name.web_archive for web-archive-based domain fingerprinting signals between agents, and v3.fingerprint.domain_name.service.http plus http.dom selectors for HTTP service and DOM fingerprinting on domain name assets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact message types but not how agents use themv2.22.14v2.22.12
Iru is a device-centric platform that unifies security, IT, and compliance around devices and everything they touch.
Iru's Windows Endpoint Agent extended its Auto Apps deployment feature to support ZIP-packaged applications.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
ZIP support for Auto Apps on Windowsimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Iru Agent for Windows now installs Auto Apps packaged as ZIP files, extending the Auto Apps deployment mechanism beyond its previous format support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Varonis introduced the MCP GatewayMCP GatewayA server that sits between MCP clients and one or more Model Context Protocol backends, routing tool calls and aggregating context sources so a single endpoint exposes many AI-agent integrations at once. within its Atlas AI Gateway, giving organizations a single control point to govern which tools, APIs, agents, 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. servers can act on behalf of users.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Varonis connects data, AI, and threat detection into one complete security platform that allows companies to keep innovating, without increasing risk.
Varonis introduced the MCP GatewayMCP GatewayA server that sits between MCP clients and one or more Model Context Protocol backends, routing tool calls and aggregating context sources so a single endpoint exposes many AI-agent integrations at once. within its Atlas AI Gateway, giving organizations a single control point to govern which tools, APIs, agents, 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. servers can act on behalf of users.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
MCP Gateway for agent tool access controlnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
The MCP Gateway is a single control point within the Atlas AI Gateway that enforces identity-aware rules over which tools, APIs, agents, and MCP servers can be reached and which actions they may perform.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Atlas validates agent identity through existing identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. using delegated credentials so agents operate under real user permissions rather than broad standing access, and every tool call is tied to a real user identity and recorded alongside prompts in an investigation timeline for accountability.
— Explains mechanism and identity model but no config/API names or steps.snapshot-20261112
AmneziaWG-installer v6.3.1 adds a repair path for kernel module issues after OS upgrades, source-address control for cascade tunnels, and tightens how obfuscation parameters and exit-address validation are generated.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
AmneziaWG-installer is a script that installs AmneziaWG, a modified WireGuard VPN with obfuscation features to bypass deep packet inspection and censorship.
AmneziaWG-installer v6.3.1 adds a repair path for kernel module issues after OS upgrades, source-address control for cascade tunnels, and tightens how obfuscation parameters and exit-address validation are generated.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Repair-module flag for kernel helpernew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Running install_amneziawg_en.sh --repair-module deploys the new module helper version 4 and rebuilds the kernel module without triggering a full install, intended for use after a 24.04 HWE-to-26.04 upgrade where DKMSDKMSA framework, maintained by the Linux community, that automatically recompiles and reinstalls kernel modules whenever the kernel is updated, so out-of-tree drivers survive upgrades without manual intervention. had cached the old build.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
After upgrading a server from Ubuntu 24.04 HWE to 26.04, redeploy the module helper and rebuild the kernel module without re-running the full install.
— Names exact flag, version, and upgrade scenario it fixesv6.3.1
0200
AWG1_SRC for cascade-tunnel source addressnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
The new AWG1_SRC setting gives cascade-tunnel source-address control, letting traffic to the exit server be routed from a specific address on an entry server that has multiple public IPv4 addresses, rather than sharing the main interface IP.
In a cascade setup where the entry server has multiple public IPv4 addresses, route tunnel traffic to the exit server from a specific third address so it does not share the main interface IP.
bash
AWG1_SRC=203.0.113.3
— Names exact variable with a working config examplev6.3.1
0300
S4=16 excluded from parameter generatorimproved73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
The parameter generator now excludes S4 = 16 from the allowed range (4–27 in the 2.0 profile, 12–27 in 3.1), so new installs no longer produce packet lengths that are multiples of 16 at every payload size, matching a pattern plain WireGuardWireGuardA modern VPN protocol and Linux kernel module, maintained as an open-source project, that establishes encrypted tunnels using minimal code and fast cryptography, giving cyber tools a lightweight, high-performance transport layer. packets exhibit and that could aid detection.
— Names exact parameter and ranges, no direct command givenv6.3.1
thinner coverage below
0400
Exit-address validation against DNS-resolved namesimproved20how completely this was documenteddepth10/40specificity10/30actionability0/3020 / 100
Exit-address validation is tightened against DNS-resolved entry names, per the release summary; no further mechanism or example is provided.
— Only a one-line summary mention, no detail or examplev6.3.1
1Password CLI Beta introduces a full command suite for managing 1Password Environments and their secrets, and changes how Trust Log Bookmarks are keyed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
All the latest releases from the 1Password team
1Password CLI Beta introduces a full command suite for managing 1Password Environments and their secrets, and changes how Trust Log Bookmarks are keyed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
0 FEATURES2 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
1Password Environments and secrets CLInew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds 1Password Environment management commands op environment create (returns name, ID, content version, and timestamps), op environment get (returns name, ID, content version, creation time, and last-updated time), op environment list, op environment edit (rename and return updated details), and op environment delete (by name or ID).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Also adds secret management within environments: op environment secret create (set name, value, and concealed state), op environment secret get (by name), op environment secret edit (rename, change value, or toggle concealed state), and op environment secret delete (by name).
Trust Log Bookmarks keyed by unique identifierimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Trust Log Bookmarks are now stored by a unique identifier rather than account UUIDUUIDA universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide..
RegScale is a continuous compliance automation platform that helps organizations manage security controls, audit evidence, and regulatory requirements in real time.
Nessus imports now show an overall file progress bar and log one line per file.
CISO Assistant is a one-stop-shop GRC platform for Risk Management, AppSec, Compliance & Audit, TPRM, BIA, Privacy, and Reporting. It supports 200+ global frameworks with automatic control mapping, including ISO 27001, NIST CSF, SOC 2, CIS, PCI DSS, NIS2, DORA, GDPR, HIPAA, CMMC, and more.
CISO Assistant adds evidence review mode, scenario selection across risk workflows, memcached caching, a new view_user_fullIAMIAMIdentity 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. permission, maturity scores in Framework Insights, and a dedicated third-party app shell.
└──▷ GET THIS VERSION
$ git clone --branch v4.2.3 https://github.com/intuitem/ciso-assistant-community.git
# already have the repo? check out this version:$ git checkout v4.2.3
Gate user sign-in and administration detail visibility with the new view_user_full IAM permission.
Filter risk assessments, action plans, and exports by selecting specific scenarios with the new scenario selection feature across the risk assessment workflow.
Add memcached for consistent caching and rate-limiting across the application.
Review submitted evidence in a new dedicated evidence review mode.
Show documentation and maturity scores inside Framework Insights.
+1 moreshow less
Access a dedicated app shell for third parties to differentiate them from first-party entities.
OneTrust's November 2026 CMP API update extends Web SDK (OT-Device-Type: web) support across the Log Consent, Get Banner Data, Get Preference Center Data, and Get IABIABInitial Access Broker — a threat actor who specialises in compromising networks and selling that access to other criminals, such as ransomware operators, rather than exploiting it directly. and Google Vendors APIs, while adding new OS-detection and error-code headers, A/B test variant visibility, and granular location-based reconsent.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
The OneTrust Developer Portal allows you to leverage APIs and SDKs to integrate external systems seamlessly and streamline the data flow with the OneTrust platform.
OneTrust's November 2026 CMP API update extends Web SDK (OT-Device-Type: web) support across the Log Consent, Get Banner Data, Get Preference Center Data, and Get IABIABInitial Access Broker — a threat actor who specialises in compromising networks and selling that access to other criminals, such as ransomware operators, rather than exploiting it directly. and Google Vendors APIs, while adding new OS-detection and error-code headers, A/B test variant visibility, and granular location-based reconsent.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Web consent logging and purpose notes in Log Consent APInew85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
The Log Consent API now accepts OT-Device-Type: web and web-specific interactionType values API_ALLOW_ALL, API_REJECT_ALL, API_UPDATE_CONSENT, GPC_VALUE_CHANGED, DNT_VALUE_CHANGED, ANONYMOUS_LOGGED_OUT_CONSENT, CROSS_DEVICE_SYNC_LOCAL, and NO_INTERACTION for logging consent from web implementations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It also returns canGenerateNotGivenReceipts and authenticatedLoggedOutConsent fields under appConfig to indicate receipt support, and now includes noteType and noteText alongside noteId in PurposeNote responses.
OS-detection and error-code headers on CMP APIsnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
CMP APIs add an optional OT-OS request header (Apple or Android) to identify the underlying OS in cross-platform SDKs such as .NET MAUI — it takes precedence over OT-Platform and enables OS-specific behavior for ATT and Google advertising identifiers — and a new OT-Error-Code response header that returns comma-separated unique error codes on CMP API error responses, letting callers read failures without parsing the JSON body.
Web banner data via Get Banner Data APInew73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
The Get Banner Data API, called with OT-Device-Type: web, now returns bannerUIData covering layouts, positioning, accessibility, focus management, branding, and custom styling, plus web-specific appConfig settings for geolocation handling, Google Consent Mode, Additional Consent Mode, Multi-Cookie Management, and global opt-out configuration.
Web preference center data via Get Preference Center Data APInew73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
The Get Preference Center Data API, called with OT-Device-Type: web, now returns pcUIData covering layouts, styling, branding, accordion behavior, accessibility, purpose hierarchies, GPC/DNT signals, tracking technology disclosures (cookies, local storage, session storage), and search and filtering for cookies, vendors, and tracking technologies.
Web vendor data via Get IAB and Google Vendors APInew73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
The Get IAB and Google Vendors API, called with OT-Device-Type: web, retrieves IAB TCF v2.4, Google, and general vendor data for web consent experiences, including localized labels via vendorListDescription, filterAriaLabel, searchPlaceholderText, and searchAriaLabel fields.
A/B test variant details in appConfignew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
CMP API responses now include a variant object under appConfig returning the variant id and name, letting callers confirm which banner variant was delivered and validate audience- and rule-based variant selection.
Location-specific reconsent datesnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Location-specific reconsent dates can now be applied at the state/region, country, or geolocation-rule level across CMP APIs and the Web SDK when granular geo-level reconsent is enabled.
Docker Sandboxes run AI coding agents in isolated environments on your machine or on Docker-managed cloud infrastructure
Docker Sandboxes v0.53.0 adds local disk usage reporting, Docker Hardened Image selection, Claude in Chrome support, and tunable stalled-connection timeouts for VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. recovery, alongside a cluster of CLI usability fixes and several breaking changes to agent handling, secret providers, and HTTP policy matching.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
15 FEATURES2 OF 15 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Local disk usage reporting with sbx dfnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
sbx df reports local image, container, and managed-volume disk usage and estimated reclaimable space, with --verbose giving a per-resource breakdown.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Check how much local disk space sandboxes are consuming and what could be reclaimed before running a prune.
$ sbx df --verbose
— Runnable command with exact flag and scope namedv0.53.0
0201
Docker Hardened Image selection via settingsbreaking70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Docker Hardened Image templates are now selected with sbx settings set platform.images.useDHI true, replacing the retired DOCKER_SANDBOXES_USE_DHI environment variable.
— Names exact setting key and the retired env varv0.53.0
0300
Stalled outbound connection timeoutnew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Stalled outbound connection timeouts can be tuned with egress.stalledConnectionTimeoutSeconds, or set to 0 to disable; the daemon must be restarted for the change to apply to existing sandboxes, aiding VPN recovery.
— Config key, disable value, and restart requirement all namedv0.53.0
0400
Claude in Chrome access for sandboxed Claude Codenew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Sandboxed Claude Code can now access Claude in Chrome via the claude.remoteControl and claude.chrome settings, started with --chrome on Claude Code.
— Both settings and the launch flag are namedv0.53.0
0500
sbx run entrypoint argument handling changebreaking65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
sbx run <agent> -- <args> now preserves the image's entrypoint arguments when a prompt or subcommand is passed; if the entrypoint already includes a subcommand, it should be omitted from the arguments to avoid running it twice.
— Exact command form and a concrete migration caveatv0.53.0
0600
Untagged and digest-only image listingnew60how completely this was documenteddepth15/40specificity20/30actionability25/3060 / 100
sbx template ls --all --digests --no-trunc lists untagged and digest-only local images, with full image IDs preserved in JSON and YAML output.
Find and remove dangling or digest-only local sandbox images that do not appear in a plain listing.
Secret reference provider execution changesbreaking60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Built-in secret reference providers now run host tools from a temporary directory and ignore empty or relative PATH entries; provider tools should be placed in absolute PATH directories and asdf or mise versions configured globally.
— Mechanism and remediation steps named, no exact commandv0.53.0
thinner coverage below
0800
Named sandbox selection for MCP registrationsnew55how completely this was documenteddepth15/40specificity20/30actionability20/3055 / 100
When 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. registration names are shared across sandboxes, a sandbox-owned registration can be selected by name with --sandbox on sbx mcp inspect or sbx mcp rm --registration-only.
— Exact flags and subcommands named, mechanism thinv0.53.0
0902
Flags removed from sbx exec and env execbreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
The --detach and --privileged flags have been removed from sbx exec and sbx env exec; local exec commands also now reject --detach-keys instead of silently ignoring it.
— Exact flags and commands named, no replacement givenv0.53.0
1000
sbx logout requires confirmationbreaking50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
sbx logout now requires confirmation even without a running daemon; scripts should pass --yes or -y to proceed non-interactively.
— Exact flags given to restore scripted behaviourv0.53.0
1100
HTTP policy matching now case-insensitivebreaking50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
HTTP policy matching now treats ASCII letters in URL paths and query parameter names and values case-insensitively; rules relying on case to distinguish allowed and denied requests should be reviewed.
— Behaviour change named, no example of affected rulev0.53.0
1200
Directory copy improvements in sbx cpimproved45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
sbx cp now supports copying a directory to a new path ending in / and reports a missing destination directory before uploading, rather than failing partway through.
— Names the command and the two behaviour changesv0.53.0
1300
sbx inspect discoverability and output fieldsimproved45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
sbx inspect is now listed in help and shell completion, and local JSON and YAML inspection output now includes the sandbox ID and creation time.
— Names command and new output fields, thin on mechanismv0.53.0
1400
Built-in gemini agent retiredbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
The built-in gemini agent name is retired; existing Gemini sandboxes keep running but can no longer be moved with sbx move.
— Clear before/after but no migration path givenv0.53.0
1500
Shell completion and command alias expansionimproved40how completely this was documenteddepth10/40specificity20/30actionability10/3040 / 100
Shell completion now covers pull policies, timeout actions, capture modes, shared skills modes, and move destinations. MCP listings accept list as an alias for ls, SSH setup removal accepts rm as an alias for remove, and policy checks and MCP authorization accept -v as shorthand for --verbose.
— Several named aliases and completions, no single runnable examplev0.53.0
└──▷ BREAKING ON UPGRADE
!
The built-in `gemini` agent name is retired; existing Gemini sandboxes keep running but cannot be moved with `sbx move`.Our best guess
`sbx run <agent> -- <args>` now preserves the image's entrypoint arguments when you pass a prompt or subcommand; if the entrypoint already includes a subcommand, omit it from your arguments to avoid running it twice.Our best guess
Built-in secret reference providers now run host tools from a temporary directory and ignore empty or relative `PATH` entries; put provider tools in absolute `PATH` directories and configure asdf or mise versions globally.Our best guess
`DOCKER_SANDBOXES_USE_DHI` is no longer read; use `sbx settings set platform.images.useDHI true` to select Docker Hardened Image templates.Our best guess
The `--detach` and `--privileged` flags have been removed from `sbx exec` and `sbx env exec`; local exec commands also reject `--detach-keys` instead of ignoring it.Our best guess
HTTP policy matching now treats ASCII letters in URL paths and query parameter names and values case-insensitively; review rules that rely on case to distinguish allowed and denied requests.Our best guess
h5i's v0.5.5 release adds a built-in proxy for capturing and auditing browser sessions, installable websec and recon plugins for request replay and target reconnaissance, a command for running attack-flow security regression tests, and a local activity dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
H5i is an Axum-based Rust web framework with Lean 4-verifiable application kernels that run on servers, bare-metal embedded devices, and GPUs, plus integrated security testing.
h5i's v0.5.5 release adds a built-in proxy for capturing and auditing browser sessions, installable websec and recon plugins for request replay and target reconnaissance, a command for running attack-flow security regression tests, and a local activity dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES0 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Browser session capture via built-in proxynew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Run browser sessions through a built-in proxy with h5i browser open <url>, h5i browser snapshot, h5i browser requests, and h5i browser audit — every request is policy-checked and logged before it moves.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Inspect every HTTP request a browser session made — and what was refused — after an automated audit run.
— Names four commands and the policy-check/log mechanism.v0.5.5
0200
Websec HTTP workbench pluginnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Install the websec plugin with h5i plugin install websec --from ./h5i-websec to get an HTTP workbench that replays and modifies captured requests, e.g. h5i websec replay req_42 --set query.id=456.
Replay a captured request with a modified parameter to test how the target handles tampered input.
$ h5i websec replay req_42 --set query.id=456
— Install and replay commands with a flag example are fully runnable.v0.5.5
0300
Attack-flow security regression testingnew72how completely this was documenteddepth22/40specificity20/30actionability30/3072 / 100
Run h5i test <path> --target <url> to execute attack-flow tests against a target, with every request allowlist-checked and logged before any bytes move.
— Runnable command with allowlist/logging mechanism described.v0.5.5
thinner coverage below
0400
Recon plugin for target enumerationnew55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Install the recon plugin with h5i plugin install recon --from ./h5i-recon to record what a target exposes, tracking each candidate URL to the stored message that confirmed it.
— Install command given but no further subcommands named.v0.5.5
0500
Local activity dashboardnew35how completely this was documenteddepth10/40specificity10/30actionability15/3035 / 100
Launch a local dashboard with h5i ui to view browser and session activity.
— Command named but scope of what's shown is vague.v0.5.5
Tenuo's v0.3.7 release adds optional argument support with presence-aware constraints, a Python preflight attenuation checker, multi-party approval builders, and OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant.-based HelmHelmA package manager for Kubernetes, maintained by the CNCF, that lets tools define, version, and deploy clusters of Kubernetes resources as a single reusable unit called a chart. chart distribution, alongside breaking changes to type coercion in constraint matching.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES1 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Authorizer Helm chart via GHCR OCI artifactnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
The authorizer Helm chart can now be installed directly from GHCRGHCRGitHub Container Registry, GitHub's hosted service for storing and distributing OCI-compatible container images, giving cyber tools a versioned, access-controlled image store tied directly to a GitHub repository. as an OCI artifact using helm upgrade --install tenuo-authorizer oci://ghcr.io/tenuo-ai/charts/tenuo-authorizer --version 0.3.7; an immutable digest sha256:c6dcd5a07178d2161f1397b947796e54b025e69eb43520514a7cfe57e2a68cba is attached and recorded in chart-reference.txt.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Deploy the authorizer from the immutable OCI Helm chart on GHCR without a separate chart repository.
— Exact runnable command, version, and immutable digest givenv0.3.7
0200
Optional arguments in constraint enginenew87how completely this was documenteddepth35/40specificity27/30actionability25/3087 / 100
Arguments can now be omitted entirely while still enforcing their value constraint when supplied, via ConstraintSet::insert_optional in the Rust constraint engine; diagnostics, signed CBOR warrants, and attenuation all preserve this presence rule, and a required argument cannot become optional during delegation. Warrants using this optional argument metadata require compatible verifiers — upgrade receivers before issuing them, since strict older decoders reject the metadata and older permissive decoders treat the arguments as required.
Mark a tool argument as optional so callers may omit it entirely, but enforce the value constraint whenever they do supply it.
rust
use tenuo::ConstraintSet;
let mut cs = ConstraintSet::new();
cs.insert_optional("replicas", constraint);
— Names exact method, behaviour, and upgrade/compatibility caveatv0.3.7
0301
Breaking change to Exact/OneOf type coercionbreaking85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Annotated constraint checks and the A2AA2AAgent2Agent, an open protocol started by Google for AI agents from different vendors to discover each other, delegate tasks and exchange results. It complements MCP, which connects an agent to tools. server no longer convert an argument to a string before comparing with Exact or OneOf; a policy using a number as a string such as Exact("8080") or OneOf(["1", "2"]) no longer matches an integer argument and the call is denied — write the typed literal instead, e.g. Exact(8080), OneOf([1, 2]). A2A grants now preserve the JSON types of OneOf and NotOneOf instead of coercing to strings, and Exact, OneOf, and NotOneOf now reject bytes and bytearray literals.
— Gives exact before/after examples and migration fix, no runnable snippetv0.3.7
0400
Python validate_attenuation() preflight checknew75how completely this was documenteddepth28/40specificity22/30actionability25/3075 / 100
The new Python validate_attenuation(parent, child) function checks cross-type constraint narrowing before issuing a warrant, raising typed exceptions on mismatch, and uses the same Rust core as grants and authorization so results match actual enforcement.
Preflight-check that a child warrant's constraints are a valid narrowing of a parent's before issuing, to catch policy errors early without a full round-trip.
python
from tenuo import validate_attenuation
validate_attenuation(parent_warrant, child_warrant)
— Has runnable example but limited mechanism detailv0.3.7
thinner coverage below
0500
Multi-party approval requirements in buildersnew59how completely this was documenteddepth22/40specificity22/30actionability15/3059 / 100
Python grant and native attenuation builders gain add_approvers() and raise_min_approvals() to add multi-party approval requirements, backed by the existing monotone Rust operations.
— Names the two methods but no usage example givenv0.3.7
└──▷ BREAKING ON UPGRADE
!
`Annotated` constraint checks and the A2A server no longer convert an argument to a string before comparing with `Exact` or `OneOf`; a policy using a number as a string such as Exact("8080") or OneOf(["1", "2"]) no longer matches an integer argument and the call is denied — write the typed literal instead: Exact(8080), OneOf([1, 2]).Our best guess
A2A grants now keep the JSON types of `OneOf` and `NotOneOf` values instead of converting them to strings; policies that relied on string coercion will behave differently.Our best guess
Warrants using optional argument metadata require compatible verifiers; upgrade receivers before issuing these warrants — strict older decoders reject the metadata, and older permissive decoders treat the arguments as required.Our best guess
minimal's biggest addition this window is the Box Egress Proxy (bep), a certificate-issuing, hash-chained-audit egress gatekeeper for agent boxes, alongside new secret storage, per-run network/egress flags, GitHub sign-in, box audit-trail tooling, and a git credential helper plus port proxying inside grant boxes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Minimal is a secure, declarative runtimes for Claude Code, Gemini, Codex, Pi and more, so you can run multiple agents safely on your stack from a verified software supply chain.
minimal's biggest addition this window is the Box Egress Proxy (bep), a certificate-issuing, hash-chained-audit egress gatekeeper for agent boxes, alongside new secret storage, per-run network/egress flags, GitHub sign-in, box audit-trail tooling, and a git credential helper plus port proxying inside grant boxes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
12 FEATURES1 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
Box audit trail toolingnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
min box audit reads a box's hash-chained audit trail, merging parent chains with --parent; min doctor reports an edited chain, and min box spec lists each store reference with its authorities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Inspect a box's hash-chained audit trail and merge its parent chain for a full 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. view.
$ min box audit --parent my-box
Review the full audit trail for a box, merging its parent chain, to verify no egress decisions were tampered with.
$ min box audit --parent my-box
Review the full, hash-chained audit trail for a box — including entries from its parent — to verify no egress decision was tampered with.
$ min box audit --parent mybox
Inspect the full hash-chained audit trail for a box, including its parent chain, to verify no decisions were tampered with.
$ min box audit --parent mybox
Inspect the full audit trail for a box, merging its parent chain, to verify no proxy decisions were tampered with.
$ min box audit --parent mybox
— Multiple exact commands with repeated runnable examples across releasesrelease-de6a590f
0201
Box Egress Proxy (bep)new85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
minimal adds the Box Egress Proxy (bep), which issues leaf certificates under a name-constrained root and signing CA, keeps hash-chained audit records, and supports signing CA rotation (keys held in the Secure Enclave inside bep.app, rotated through the control socket). bep serve bounds its client-key registry with --max-client-keys, wires redemption decisions and declared egress, and injects store handles; store rules under min --config-dir are kept in step with bep serve. A signed, notarized bep ships beside minvmd on macOS, and minvmd starts the Box Egress Proxy beside gvproxy so git and gh reach GitHub from inside the VM.
Vulnerability reporting commandimproved75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Report a suspected vulnerability with min diag --security, later carried forward as min bug --security; the report now attaches the local telemetry spool and redacts telemetry settings.
File a suspected security vulnerability report to Minimal from the CLI, attaching the local telemetry spool for context.
$ min diag --security
File a suspected vulnerability in the tool itself for responsible disclosure.
Per-run network and egress flagsnew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
min task run and min box run take --network and --egress flags to control per-invocation network and egress policy.
— Exact flags and commands named, no deeper mechanismrelease-de6a590f
0500
GitHub sign-in via min loginnew70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
min login is the GitHub sign-in entry point, completing sign-in on a real page with repository choice available; logging out deletes the sign-in and refuses every reference to it.
Authenticate with GitHub under the published App so grant boxes can reach GitHub without a manual PATPATA 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..
$ min login
— Exact command and flow described, underlying mechanism not detailedrelease-de6a590frelease-6bddc077
0600
OpenTelemetry tracing stack (mlog)new65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
An opt-in 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. export stack (mlog) adds switches and a local spool, carrying one trace per request across min and minimald, spanning into minvmd VM guests.
Secret storage via min secretnew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
min secret stores, lists, and removes secrets, including min secret set with fixed-token presets.
— Exact command and subcommand named, mechanism thinrelease-de6a590f
0800
Grant box git credential helper and port proxyingnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Grant boxes ship a git credential helper so agents can pull and push without a manually pasted PAT, and minimald proxies runtime-published ports like a direct connection, steering credentialed names to the proxy and failing closed while the proxy is down.
Signed notarized minzoned app bundlenew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Ships minzoned in a signed, notarized macOS app bundle with an app icon.
— Names binary and packaging, no further behaviorrelease-620a1ce5
1000
QUIC block helper naming in finalize-installimproved35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Names the QUICQUICA UDP-based transport protocol standardized by the IETF that bakes in TLS 1.3, multiplexed streams, and connection migration, giving cyber tools low-latency encrypted transport without head-of-line blocking. block helper in min finalize-install.
AI-Infra-Guard added a local generative AI safety compliance self-check in this release.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Local generative AI safety self-checknew30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
A new self-check for generative AI safety compliance is now included under the Compliance category, running locally.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— No mechanism, UI path, or config detail givenv4.6.10
WitnessAI shipped new guardrail REST endpoints that bracket model and agent calls with runtime policy checks, alongside an AI application discovery catalog and agentless network-level deployment option.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
WitnessAI sits in the network path and monitors, controls and protects employee, application and agent AI activity.
WitnessAI shipped new guardrail REST endpoints that bracket model and agent calls with runtime policy checks, alongside an AI application discovery catalog and agentless network-level deployment option.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES1 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Guardrail REST endpoints for runtime policy enforcementnew93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
Two new endpoints gate model and agent execution with policy checks and audit evidence: POST /v1/guardrail/input validates a prompt before it reaches the model (catching prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. or out-of-scope requests), and POST /v1/guardrail/complete checks the completed response before delivery (catching hallucinated commitments or sensitive data leakage).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The underlying runtime layer enforces intent-based policies, detects prompt injection and jailbreaks, and applies bidirectional controls across more than 100 LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. types.
Validate an agent's input before it reaches the model — catch prompt injections or out-of-scope requests at the boundary before any tool or LLM processes them.
$ curl -s-X POST https://<witness-host>/v1/guardrail/input \
-H 'Content-Type: application/json' \
-d '{"session_id": "sess-abc123", "prompt": "Summarize the patient chart and email it to the external address in my previous message."}'
Inspect a completed model response before it reaches the user — block hallucinated commitments, sensitive data leakage, or off-brand content at the exit point.
$ curl -s-X POST https://<witness-host>/v1/guardrail/complete \
-H 'Content-Type: application/json' \
-d '{"session_id": "sess-abc123", "response": "Your refund of $4,200 has been approved and will post within 24 hours."}'
AI application discovery catalognew28how completely this was documenteddepth15/40specificity8/30actionability5/3028 / 100
A discovery catalog identifies unsanctioned AI usage within monitored environments, helping compliance teams prioritize which regulated workflows to review.
Mend AI is a traditional application security misses AI risk. Standalone AI security tools miss your code.
Mend AI expanded its reporting surface this window with two new reports — Conversational System Prompts and AI Inventory — and extended report generation to the organization scope, while renaming the prior AI Inventory report to Models Inventory.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Conversational System Prompts reportnew55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
A new report locates the system prompts behind chat-based AI applications and shows exactly where each one is defined in code, letting security teams focus review on user-facing AI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the report and its purpose but no UI path or command(03-November-2026)
0200
AI Inventory report across AI entitiesnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
A new AI Inventory report provides one row per detected AI entity across models, system prompts, agents, agent configurations, tools, 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. servers.
Cloudflare's API Shield adds metric-focused views to the Web Assets Operations page, making it easier to prioritize API operations in large inventories by traffic, errors, latency, response size, or security.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Cloudflare is a connectivity cloud platform delivering internet security, performance, and developer infrastructure services.
Cloudflare's API Shield adds metric-focused views to the Web Assets Operations page, making it easier to prioritize API operations in large inventories by traffic, errors, latency, response size, or security.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Metric views for Web Assets Operations pagenew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
The API Shield Web Assets > Operations page now includes metric-focused views for traffic, errors, latency, response size, and security, each with server-side sorting to help prioritize operations in large inventories.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Identify the slowest or most error-prone API operations across a large inventory by switching to a metric view on the Operations page.
📍In the Cloudflare dashboard, go to API Shield › Web Assets › Operations, then select a metric view (Traffic, Errors, Latency, Response Size, or Security) and click a column header to sort server-side.