fork-ts-checker-webpack-plugin 4.1.1

Runs typescript type checker and linter on separate process.

fork-ts-checker-webpack-plugin@4.1.1 was published on 2020-03-22. Its manifest declares 7 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.11.5.

All fork-ts-checker-webpack-plugin versions · Permanent reference to 4.1.1 · Latest release

Package specifications

Version4.1.1
License declarationMIT
Published2020-03-22T19:04:50.824Z
Node.js requirement>=6.11.5
Type declarationsBundled declarations
Runtime dependency count7
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size230.17 KiB
Published file count116
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies123
Repository stars2000
Repository forks256

Install fork-ts-checker-webpack-plugin 4.1.1

npm install fork-ts-checker-webpack-plugin@4.1.1
pnpm add fork-ts-checker-webpack-plugin@4.1.1
yarn add fork-ts-checker-webpack-plugin@4.1.1

Runtime dependencies

Peer requirements

  • None declared

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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review5/10 — Found 9/16 approved changesets -- score normalized to 5
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness