</>PackageGraphPackageGraph

is-core-module

npmv2.16.2

Is this specifier a node.js core module?

Safe to adopt

Yes — is-core-module scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 127 days ago. 3 releases in the last 2 years.

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

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 127 days ago. 3 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 2 transitive packages, about 78 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-core-module to a project.

1
Direct dependencies

Runtime packages this one declares itself.

2
Total installed

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

78 KB
Install size

Unpacked size of this package plus its entire runtime tree.

2
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

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

Compatibility

Node.js
node >= 0.4
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the is-core-module README.

jsFull README ↗
var isCore = require('is-core-module');
var assert = require('assert');
assert(isCore('fs'));
assert(!isCore('butts'));

is-core-module 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-core-modulethis page01MIT4 months ago
esm6.2M5MIT1 day ago
import-meta-resolve03MIT1 day ago
resolve02MIT1 day ago
lodash147.8M20MIT1 day ago
axios106.5M4MIT1 day ago

Dependencies

Declared by is-core-module v2.16.2. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

hasown ^2.0.3

Dev (11)

@ljharb/eslint-config ^22.2.3auto-changelog ^2.5.0encoding ^0.1.13eslint ^8.57.1in-publish ^2.0.1mock-property ^1.1.0npmignore ^0.3.5nyc ^10.3.2safe-publish-latest ^2.0.0semver ^6.3.1tape ^5.9.0

Used by

Popular packages that depend on is-core-module.

resolvenpm

resolve like require.resolve() on behalf of files asynchronously and synchronously

↓ 0/wk◈ 2 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of is-core-module.

hasownresolveis-core-module
is-core-module dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
supports-preserve-symlinks-flagnpm

Determine if the current node version supports the `--preserve-symlinks` flag.

↓ 46.3M/wk◈ 1 dependents⚖ MIT
semvernpm

The semantic version parser used by npm.

↓ 0/wk◈ 55 dependents⚖ ISC
jitinpm

Runtime typescript and ESM support for Node.js

↓ 0/wk◈ 15 dependents⚖ MITTS
es-errorsnpm

A simple cache for a few of the JS Error constructors.

↓ 0/wk◈ 15 dependents⚖ MITTS
path-parsenpm

Node.js path.parse() ponyfill

↓ 0/wk◈ 1 dependents⚖ MIT

Release history

3 releases in the last two years, typically about 75 days apart.

Recent versions of is-core-module
VersionPublishedSizeLicense
2.16.2latest4 months ago38 KBMIT
2.16.11 year ago33 KBMIT
2.16.01 year ago32 KBMIT
2.15.12 years ago32 KBMIT
2.15.02 years ago31 KBMIT
2.14.02 years ago30 KBMIT
2.13.12 years ago30 KBMIT
2.13.03 years ago29 KBMIT
2.12.13 years ago29 KBMIT
2.12.03 years ago28 KBMIT
2.11.03 years ago27 KBMIT
2.10.04 years ago27 KBMIT
2.9.04 years ago26 KBMIT
2.8.14 years ago25 KBMIT
2.8.04 years ago24 KBMIT

Overview

is-core-module is an npm package that is this specifier a node.js core module?. It has 1 known dependents in the graph. The latest version is 2.16.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need is this specifier a node.js core module? and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

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

Maintainers

ljharb

Keywords

coredependenciesmodulemodulesnodenpm

Funding

Frequently asked questions

Should I use is-core-module?

Yes — is-core-module scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 127 days ago. 3 releases in the last 2 years.

How do I install is-core-module?

Run `npm install is-core-module` to add is-core-module to your npm project.

How many dependencies does is-core-module have?

is-core-module declares 12 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 78 KB on disk.

What license is is-core-module released under?

is-core-module is distributed under the MIT license.

How popular is is-core-module?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on is-core-module.

Is is-core-module still maintained?

The most recent release of is-core-module (v2.16.2) was published 4 months ago.

Does is-core-module run install scripts?

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