# How can I generate the full list of dependencies required to build a Kibana plugin in airgapped env?

**URL:** <https://discuss.elastic.co/t/how-can-i-generate-the-full-list-of-dependencies-required-to-build-a-kibana-plugin-in-airgapped-env/386297>\
**Category:** Kibana\
**Tags:** kibana-plugin-development\
**Created:** [May 12, 2026, 6:05am UTC](https://discuss.elastic.co/t/how-can-i-generate-the-full-list-of-dependencies-required-to-build-a-kibana-plugin-in-airgapped-env/386297 "2026-05-12T06:05:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rishav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rishav/32/140744_2.png) [@Rishav](https://discuss.elastic.co/u/Rishav)\
**Post date:** [May 12, 2026, 6:05am UTC](https://discuss.elastic.co/t/how-can-i-generate-the-full-list-of-dependencies-required-to-build-a-kibana-plugin-in-airgapped-env/386297/1 "2026-05-12T06:05:08Z")

</div>

We currently build our Kibana plugins in a CI/CD pipeline on a VM with full internet access. As part of a security hardening effort, we are moving this build to an airgapped environment where all dependencies must be resolved from an internal private registry instead of public sources.

Before we can mirror these artifacts internally, we need to enumerate the complete set of dependencies a Kibana plugin build pulls over the network and any other build-time downloads.

Is there a recommended way to generate this complete dependency manifest, or has anyone here set up an airgapped Kibana plugin build and can share their approach?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [July 6, 2026, 9:34am UTC](https://discuss.elastic.co/t/how-can-i-generate-the-full-list-of-dependencies-required-to-build-a-kibana-plugin-in-airgapped-env/386297/2 "2026-07-06T09:34:18Z")

</div>

Hi @Rishav,

I'm aware you asked this question a while ago. But to answer, you can find the list of Kibana dependencies [in the artifact report](https://artifacts.elastic.co/reports/dependencies/dependencies-current.html#kibana-9.4.3).

For your specific plugin, it might be worth trying [npm ls](https://stackoverflow.com/questions/25997519/how-to-view-the-dependency-tree-of-a-given-npm-module):

```auto
npm ls --all

```

Hope that helps!