typescript-eslint-parser 0.1.3
An Esprima-style parser for TypeScript
typescript-eslint-parser@0.1.3 was published on 2016-08-22. 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 >=0.10.0.
All typescript-eslint-parser versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | BSD-2-Clause |
| Published | 2016-08-22T23:40:59.554Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | parser.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 911 |
| Repository forks | 72 |
Install typescript-eslint-parser 0.1.3
npm install typescript-eslint-parser@0.1.3 pnpm add typescript-eslint-parser@0.1.3 yarn add typescript-eslint-parser@0.1.3
Runtime dependencies
- lodash.unescape 4.0.0
- object-assign ^4.0.1
Peer requirements
- typescript ^1.7.3
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- lodash.tostring@4.1.4 — indirect
- lodash.unescape@4.0.0 — direct
- object-assign@4.1.1 — direct
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.
| Code-Review | 7/10 — Found 22/30 approved changesets -- score normalized to 7 |
|---|---|
| Maintained | 0/10 — project is archived |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Security-Policy | 10/10 — security policy file detected |
| Branch-Protection | 5/10 — branch protection is not maximal on development and all release branches |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/typescript-eslint-parser/0.1.3 — retrieved 2026-10-31T20:21:17.469Z
- https://api.deps.dev/v3/systems/npm/packages/typescript-eslint-parser/versions/0.1.3 — retrieved 2026-10-31T20:21:17.948Z
- https://api.deps.dev/v3/systems/npm/packages/typescript-eslint-parser/versions/0.1.3:dependencies — retrieved 2026-10-31T20:21:17.971Z
- https://api.deps.dev/v3/projects/github.com%2Feslint%2Ftypescript-eslint-parser — retrieved 2026-10-31T20:21:18.357Z