Along with other restrictions, we run analysis engines with no network access (via the --net none option to docker run).

We do this (primarily) because engines have access to customer source code and so a malicious actor could use an engine to access and transmit sensitive data via a network request. Because we aim to produce and maintain many engines together with the open source community, we restrict network access in this way to ensure our customers' source code is kept as safe as possible.

Unfortunately, this restriction prevents a number of real use cases and features. For example, the Rubocop engine can't install custom cops as gems or inherit a remote configuration. Similarly, ESLint can't install shared configuration or custom plugins that are distributed as node modules.

We do intend to support these use cases in some way in the future, but our focus is on security and until we can provide a way to do so safely, we're not comfortable providing a timeline on building this feature.

We apologize for this inconvenience and will keep this Issue open to track it and provide any updates from our side.