pkg-types
npmv2.3.3TypeScriptNode.js utilities and TypeScript definitions for `package.json` and `tsconfig.json`
Safe to adopt
Yes — pkg-types scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 2 days ago. 12 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 2 days ago. 12 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 3 transitive packages, about 154 KB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- 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 pkg-types to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing pkg-types, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the pkg-types README.
import { readPackage } from "pkg-types";
const localPackage = await readPackage();
// or
const pkg = await readPackage("/fully/resolved/path/to/folder");Dependencies
Declared by pkg-types v2.3.3. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (3)
Dev (12)
Used by
Popular packages that depend on pkg-types.
Missing ECMAScript module utils for Node.js
Runtime typescript and ESM support for Node.js
Get information on local packages.
Unified Package Manager for Node.js
Relationship graph
Dependencies (left) and dependents (right) of pkg-types.
Frequently installed together
Next generation testing framework powered by Vite
TypeScript definitions for node
Runtime agnostic JS utils
Universal filesystem path utils
V8 coverage provider for Vitest
URL utils for humans
A minimal library for executing processes in Node
An AST-based pattern checker for JavaScript.
[](https://github.com/mmkal/expect-type/actions/workflows/ci.yml)  [](ht
Elegant CLI Builder
ECMAScript parser
Prettier is an opinionated code formatter
Release history
11 releases in the last two years, typically about 50 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.3.3latest | 2 days ago | 50 KB | MIT |
| 2.3.2 | 6 days ago | 48 KB | MIT |
| 2.3.1 | 4 months ago | 45 KB | MIT |
| 2.3.0 | 1 year ago | 43 KB | MIT |
| 2.2.0 | 1 year ago | 36 KB | MIT |
| 2.1.1 | 1 year ago | 36 KB | MIT |
| 2.1.0 | 1 year ago | 35 KB | MIT |
| 2.0.1 | 1 year ago | 30 KB | MIT |
| 2.0.0 | 1 year ago | 30 KB | MIT |
| 1.3.1 | 1 year ago | 72 KB | MIT |
| 1.3.0 | 1 year ago | 72 KB | MIT |
| 1.2.1 | 1 year ago | 72 KB | MIT |
| 1.2.0 | 2 years ago | 71 KB | MIT |
| 1.1.3 | 2 years ago | 61 KB | MIT |
| 1.1.2 | 2 years ago | 61 KB | MIT |
Overview
pkg-types is an npm package that node.js utilities and TypeScript definitions for `package.json` and `tsconfig.json`. It has 4 known dependents in the graph. The latest version is 2.3.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need node.js utilities and TypeScript definitions for `package.json` and `tsconfig.json` 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.
Frequently asked questions
Should I use pkg-types?
Yes — pkg-types scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 2 days ago. 12 releases in the last 2 years.
How do I install pkg-types?
Run `npm install pkg-types` to add pkg-types to your npm project.
How many dependencies does pkg-types have?
pkg-types declares 15 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 154 KB on disk.
What license is pkg-types released under?
pkg-types is distributed under the MIT license.
How popular is pkg-types?
npm does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on pkg-types.
Is pkg-types still maintained?
The most recent release of pkg-types (v2.3.3) was published 2 days ago.
Does pkg-types run install scripts?
No. pkg-types does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.