fluent-ffmpeg 1.4.2

A fluent API to FFMPEG (http://www.ffmpeg.org)

fluent-ffmpeg@1.4.2 was published on 2013-06-28. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.0.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All fluent-ffmpeg versions · Permanent reference to 1.4.2 · View npm registry JSON · Latest release

Package specifications

Version1.4.2
License declarationNot declared
Published2013-06-28T13:41:56.535Z
Node.js requirement>=0.8.0
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies29
Repository stars8229
Repository forks933

Install fluent-ffmpeg 1.4.2

npm install fluent-ffmpeg@1.4.2
pnpm add fluent-ffmpeg@1.4.2
yarn add fluent-ffmpeg@1.4.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.

Code-Review5/10 — Found 10/17 approved changesets -- score normalized to 5
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/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