@node-minify/terser 4.0.2

terser plugin for @node-minify

@node-minify/terser@4.0.2 was published on 2018-12-13. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.0.0.

All @node-minify/terser versions · Permanent reference to 4.0.2 · Latest release

Package specifications

Version4.0.2
License declarationMIT
Published2018-12-13T14:34:55.609Z
Node.js requirement>=6.0.0
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.69 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entrylib/terser.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies9
Repository stars520
Repository forks49

Install @node-minify/terser 4.0.2

npm install @node-minify/terser@4.0.2
pnpm add @node-minify/terser@4.0.2
yarn add @node-minify/terser@4.0.2

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
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Code-Review0/10 — Found 0/7 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Binary-Artifacts9/10 — binaries present in source code
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness