# Seal Apps

**Seal Apps** remediates vulnerabilities in your application's third-party open-source dependencies. The packages your code pulls in directly, and the packages those packages pull in transitively, are replaced with sealed versions of the same origin versions.

## What it covers

Application-dependency ecosystems:

* **JavaScript:** npm, Yarn, pnpm
* **Python:** pip, Poetry
* **Java:** Maven, Gradle
* **Go:** Go modules
* **PHP:** Composer
* **Ruby:** Bundler
* **.NET:** NuGet

Seal Apps does not cover language runtimes themselves (the Node.js binary, the Python interpreter, the JVM, the .NET CLR). Those are handled by [Seal OS](/new-documentation/new-docs/product-family/seal-os.md) when installed via OS package managers, or by [Seal Base Images](/new-documentation/new-docs/product-family/seal-base-images.md), [Seal My Container](/new-documentation/new-docs/product-family/seal-my-container.md), or [Seal Vendor Apps](/new-documentation/new-docs/product-family/seal-vendor-apps.md) when bundled in container images.

## How it is delivered

Seal Apps uses [build-time dependency sealing](/new-documentation/new-docs/seal-approach/sealing-approaches.md). It supports several deployment methods:

* The **Seal CLI in your CI/CD pipeline** (recommended). The CLI ensures that sealed versions are used in place of vulnerable origin versions; your build proceeds as before, and the artifact you ship incorporates the sealed dependencies.
* The **Seal Artifact Server** as a configured remote (or as an additional remote) in your package manager.
* **Manual download** of sealed versions directly from the Repository page.

## Related

* [Choosing your deployment method](https://github.com/seal-community/gitbook/blob/main/new-docs/setup-apps-os/choosing-deployment-method.md): day-1 setup options for Seal Apps.
* [Working with Seal Apps](https://github.com/seal-community/gitbook/blob/main/new-docs/using-platform/working-with-seal-apps.md): the day-to-day workflow.


---

# Agent Instructions: 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:

```
GET https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.