</>PackageGraphPackageGraph

is-inside-container

npmv1.0.0TypeScript

Check if the process is running inside a container (Docker/Podman)

Not recommended for new projects

No — is-inside-container should not be adopted for new projects. Last published 1303 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1303 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package, about 6.8 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding is-inside-container to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

6.8 KB
Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing is-inside-container, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >=14.16
Module format
ESM only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the is-inside-container README.

jsFull README ↗
import isInsideContainer from 'is-inside-container';

if (isInsideContainer()) {
	console.log('Running inside a container');
}

is-inside-container vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
is-inside-containerthis page02MIT3 years ago
is-docker02MIT1 day ago
is-wsl117.6M4MIT1 day ago
is-in-ssh01MIT1 day ago
path-key244.9M1MIT1 day ago
has-flag166.9M1MIT1 day ago

Dependencies

Declared by is-inside-container v1.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

is-docker ^3.0.0

Dev (4)

ava ^5.2.0esmock ^2.1.0tsd ^0.25.0xo ^0.53.1

Used by

Popular packages that depend on is-inside-container.

opennpm

Open stuff like URLs, files, executables. Cross-platform.

↓ 130.4M/wk◈ 4 dependents⚖ MITTS
is-wslnpm

Check if the process is running inside Windows Subsystem for Linux (Bash on Windows)

↓ 117.6M/wk◈ 4 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of is-inside-container.

is-dockeropenis-wslis-inside-contain…
is-inside-container dependencies dependents

Frequently installed together

default-browsernpm

Get the default browser

↓ 52.6M/wk◈ 1 dependents⚖ MITTS
wsl-utilsnpm

Utilities for working with Windows Subsystem for Linux (WSL)

↓ 42.8M/wk◈ 1 dependents⚖ MITTS
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
is-in-sshnpm

Check if the process is running in an SSH session

↓ 0/wk◈ 1 dependents⚖ MITTS
define-lazy-propnpm

Define a lazily evaluated property on an object

↓ 0/wk◈ 1 dependents⚖ MIT

Release history

No releases in the last two years.

Recent versions of is-inside-container
VersionPublishedSizeLicense
1.0.0latest3 years ago3.4 KBMIT

Overview

is-inside-container is an npm package that check if the process is running inside a container (Docker/Podman). It has 2 known dependents in the graph. The latest version is 1.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need check if the process is running inside a container (Docker/Podman) and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

sindresorhus

Keywords

containerdetectdockerdockerizedenvenvironmentinsideispodmanprocess

Funding

Frequently asked questions

Should I use is-inside-container?

No — is-inside-container should not be adopted for new projects. Last published 1303 days ago.

How do I install is-inside-container?

Run `npm install is-inside-container` to add is-inside-container to your npm project.

How many dependencies does is-inside-container have?

is-inside-container declares 5 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 6.8 KB on disk.

What license is is-inside-container released under?

is-inside-container is distributed under the MIT license.

How popular is is-inside-container?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on is-inside-container.

Is is-inside-container still maintained?

The most recent release of is-inside-container (v1.0.0) was published 3 years ago.

Does is-inside-container run install scripts?

No. is-inside-container does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.