> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/changelog/q2-2026/50-agentic-dependency-autofix-registry-proxy-and-device-protection-adds-ruby-and-rust.md).

# #50 - Agentic Dependency AutoFix, Registry Proxy and Device Protection adds Ruby and Rust

### Features

* [Agentic Dependency AutoFix](https://help.aikido.dev/autofix-and-remediation/overview-aikido-autofix#dependency-autofix) - Let Aikido resolve complex dependency interactions for you. Perfect for projects with many interlocking dependencies.
* [Registry Proxy](https://help.aikido.dev/miscellaneous-integrations/private-registries) **-** Your private registry can now route through Aikido, blocking malware and risky-new packages and serving safe, patched versions before they hit your code.
* [Device Protection](https://help.aikido.dev/aikido-device-protection/endpoint-protection) - Now covers Ruby and Rust, blocking malware on install and adding gems and crates to your device SBOM.

### **Aikido Intel - Malware & Vulnerability Research**

Our research team has discovered more than [#232 new vulnerabilities](https://intel.aikido.dev) over the last two weeks! We also scanned 1.2 million newly published packages for malware and found 3,066 new ones.

Separately, our new [State of AI in Security & Development 2026](https://www.aikido.dev/state-of-ai-security-development-2026) report surveyed 450 CISOs and developers on how AI is reshaping security, including why 1 in 5 hit a serious incident from AI-generated code.

### Improvements

* AI Pentest
  * [Letter of Attestation](https://help.aikido.dev/pentests/coverage-and-findings/pentest-reports)
  * [Continuous Pentest adds Azure support](https://help.aikido.dev/pentests/continuous-pentesting)
  * [Continuous Pentest choose branches for 'On Schedule' runs](https://help.aikido.dev/pentests/continuous-pentesting#enable-continuous-pentesting)
* Labels - [Import labels directly from Github](https://help.aikido.dev/getting-started/manage-teams-and-applications/add-labels-to-resources#import-repository-labels-from-github)
* MCP - [Release with new auth flow, workspace filters, branch filter and team filters](https://help.aikido.dev/ai-and-dev-tools/aikido-mcp)
* Code Audit - Add additional instructions before an audit
* Zen Firewall - Agent releases for [Dotnet](https://github.com/AikidoSec/firewall-dotnet/releases), [Python](https://github.com/AikidoSec/firewall-python/releases), [PHP](https://github.com/AikidoSec/firewall-php/releases), [Golang](https://github.com/AikidoSec/firewall-go/releases) and [Node](https://github.com/AikidoSec/firewall-node/releases)
* IDE - New releases for [Jetbrains](https://plugins.jetbrains.com/plugin/24993-aikido-security/versions/stable)
* API - [Manage labels on repositories](https://apidocs.aikido.dev/reference/addcoderepolabel)
* API - [List container runners](https://apidocs.aikido.dev/reference/listcontainerreporunners)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.aikido.dev/changelog/q2-2026/50-agentic-dependency-autofix-registry-proxy-and-device-protection-adds-ruby-and-rust.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.