officeparser 6.0.7

A robust, strictly-typed Node.js and Browser library for parsing office files (.docx, .pptx, .xlsx, .odt, .odp, .ods, .pdf, .rtf) into structured AST with rich metadata, formatting, and attachment support.

officeparser@6.0.7 was published on 2026-03-24. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.0.0.

All officeparser versions · Permanent reference to 6.0.7 · Latest release

Package specifications

Version6.0.7
License declarationMIT
Published2026-03-24T11:32:36.586Z
Node.js requirement>=18.0.0
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2899.80 KiB
Published file count38
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies47
Repository stars561
Repository forks56

Install officeparser 6.0.7

npm install officeparser@6.0.7
pnpm add officeparser@6.0.7
yarn add officeparser@6.0.7

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
Maintained10/10 — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
SAST0/10 — no SAST tool detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Packaging10/10 — packaging workflow detected

Evidence and freshness