@videojs/http-streaming 0.2.0

Play back HLS with video.js, even where it's not natively supported

@videojs/http-streaming@0.2.0 was published on 2017-12-14. Its manifest declares 9 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.12.

All @videojs/http-streaming versions · Permanent reference to 0.2.0 · View npm registry JSON · Latest release

Package specifications

Version0.2.0
License declarationApache-2.0
Published2017-12-14T20:07:55.818Z
Node.js requirement>= 0.10.12
Type declarationsNot declared
Runtime dependency count9
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 entryes5/videojs-http-streaming.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies40
Repository stars2665
Repository forks440

Install @videojs/http-streaming 0.2.0

npm install @videojs/http-streaming@0.2.0
pnpm add @videojs/http-streaming@0.2.0
yarn add @videojs/http-streaming@0.2.0

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review6/10 — Found 18/30 approved changesets -- score normalized to 6
Maintained1/10 — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness