typescript-estree

A parser that converts TypeScript source code into an ESTree compatible form

typescript-estree@18.1.0 was published on 2019-01-13. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.14.0.

Deprecated: This package was moved to @typescript-eslint/typescript-estree, please install the latest version from there instead

All typescript-estree versions · Permanent reference to 18.1.0

Package specifications

Version18.1.0
License declarationBSD-2-Clause
Published2019-01-13T20:38:07.649Z
Node.js requirement>=6.14.0
Type declarationsNot declared
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size215.37 KiB
Published file count29
Package typeNot declared
ES module entryNot declared
Default entrydist/parser.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars85
Repository forks13

Install typescript-estree 18.1.0

npm install typescript-estree@18.1.0
pnpm add typescript-estree@18.1.0
yarn add typescript-estree@18.1.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — project is archived
Code-Review7/10 — Found 21/30 approved changesets -- score normalized to 7
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness