html2pdf.js 0.9.2

Client-side HTML-to-PDF rendering using pure JS

html2pdf.js@0.9.2 was published on 2020-02-19. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All html2pdf.js versions · Permanent reference to 0.9.2 · Latest release

Package specifications

Version0.9.2
License declarationMIT
Published2020-02-19T14:39:24.569Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size236.02 KiB
Published file count19
Package typeNot declared
ES module entrydist/include/html2pdf.es.js
Default entrydist/require/html2pdf.cjs.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies92
Repository stars4927
Repository forks1719

Install html2pdf.js 0.9.2

npm install html2pdf.js@0.9.2
pnpm add html2pdf.js@0.9.2
yarn add html2pdf.js@0.9.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.

Known direct advisories

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
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness