> 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/45-aikido-lovable-vibe-fix-ship-and-container-reachability.md).

# #45 - Aikido × Lovable - Vibe, Fix, Ship and Container Reachability

10 Apr 2026

### Features

* [**Aikido × Lovable**](https://www.aikido.dev/partners/aikido-lovable) - Vibe, Fix, Ship. Aikido now offers integrated pentesting for Lovable, helping teams find and fix security issues before launch.
* [**Container reachability**](https://help.aikido.dev/container-image-scanning/container-reachability-analysis) - Map the complete network route to your running containers and view CVEs in a deployment context, so you can see what's reachable from the internet.

<figure><img src="https://2617374768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVpXs0098tjeCDdymgyXm%2Fuploads%2FyVBf5nm0Gkn37cVMU9Nc%2Fimage.png?alt=media&amp;token=b972f1eb-e29c-42fb-9329-4517bffc381d" alt=""><figcaption></figcaption></figure>

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

Our research team discovered more than [#60 new vulnerabilities](https://intel.aikido.dev) over the last two weeks! Read the detailed blog posts on the [GlassWorm Zig dropper](https://www.aikido.dev/blog/glassworm-zig-dropper-infects-every-ide-on-your-machine) and the [compromised axios npm package maintainer hijack](https://www.aikido.dev/blog/axios-npm-compromised-maintainer-hijacked-rat).

Explore [Safe Chain on GitHub](https://github.com/AikidoSec/safe-chain), our open-source tool that helps stop compromised packages like axios from reaching your codebase.

### Improvements

* Containers - [Detect org.opencontainers.image.source tags in docker images](https://help.aikido.dev/container-image-scanning/configuration/link-containers-to-code-repositories-via-docker-labels)
* Virtual Machines - [Reachability is now available for Azure](https://help.aikido.dev/virtual-machine-scanning/misc/virtual-machine-reachability-analysis)
* Zen Firewall - [Refresh of our installation flow and new installation instructions](https://help.aikido.dev/zen-firewall/zen-installation-instructions)
* Zen Firewall - Agent releases for [Dotnet](https://github.com/AikidoSec/firewall-dotnet/releases), [PHP](https://github.com/AikidoSec/firewall-php/releases), [Ruby](https://github.com/AikidoSec/firewall-ruby/releases), [Golang](https://github.com/AikidoSec/firewall-go/releases) and [Node](https://github.com/AikidoSec/firewall-node/releases)
* User Management - Link SAML users to Github teams automatically
* Aikido Intel - [Added Drupal malware scanning](https://intel.aikido.dev/malware)
* Safe Chain - [New version with min package age support for Python](https://github.com/AikidoSec/safe-chain?tab=readme-ov-file#minimum-package-age)
* IDE - New releases for [VSCode](https://marketplace.visualstudio.com/items?itemName=AikidoSecurity.aikido) and [Visual Studio](https://marketplace.visualstudio.com/items?itemName=AikidoSecurity.aikido-visualstudio)
* API - [Manage webhooks](https://apidocs.aikido.dev/reference/addwebhook)
* API - [Manage excluded paths for a repository](https://apidocs.aikido.dev/reference/addcoderepoexcludepath)
* API - [Custom headers for webhooks](https://apidocs.aikido.dev/reference/webhooks)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/changelog/q2-2026/45-aikido-lovable-vibe-fix-ship-and-container-reachability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
