npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stackline/cfb

v1.0.4

Published

Read and write compound files and ZIP containers with the SheetJS CFB API and bounded FAT traversal

Readme

@stackline/cfb

Read and write compound files and ZIP containers with the SheetJS CFB API and bounded FAT traversal.

npm version license GitHub repository Docs Reddit community

Documentation | npm | Issues | Repository

Current package version: 1.0.4


Why this package?

An independent Apache-2.0 maintenance fork of [email protected].

npm install @stackline/cfb
const CFB = require('@stackline/cfb');

Version 1.0.0 preserves the upstream API and rejects cyclic FAT chains instead of hanging while parsing a damaged compound file (upstream issue SheetJS/js-cfb#11). The declared checksum runtime dependencies were unused because the implementation already embeds its checksum code; this package has no runtime dependencies.

Node.js 20.19 or newer is the supported development/runtime target. npm test builds the CommonJS/browser artifacts, runs the upstream API suite against three pinned public fixtures, and checks corrupted input and archive round trips. This selected fixture set is not the full upstream document corpus.

The original source and attribution are retained below.


Pure JS implementation of various container file formats, including ZIP and CFB.

Compatibility

| Item | Value | | --- | --- | | Package | @stackline/[email protected] | | Supported Node.js | >=20.19.0 | | Module entry | ./cfb (CommonJS) | | Runtime dependencies | 0 direct dependencies | | Types | types |

Installation

npm install @stackline/cfb

In the browser:

<script src="dist/cfb.min.js" type="text/javascript"></script>

With npm:

$ npm install @stackline/cfb

The xlscfb.js file is designed to be embedded in js-xlsx

Usage

const CFB = require('@stackline/cfb');
const archive = CFB.utils.cfb_new();
CFB.utils.cfb_add(archive, 'hello.txt', Buffer.from('Hello'));
const bytes = CFB.write(archive, { type: 'buffer', fileType: 'zip' });

Library Usage

In node:

var CFB = require('@stackline/cfb');

For example, to get the Workbook content from an Excel 2003 XLS file:

var cfb = CFB.read(filename, {type: 'file'});
var workbook = CFB.find(cfb, 'Workbook');
var data = workbook.content;

Security

The parser rejects cyclic FAT chains instead of looping indefinitely. See the security policy for supported reporting and parser limitations.

See the security policy.

API Surface

Command-Line Utility Usage

The cfb-cli module ships with a CLI tool for manipulating and inspecting supported files.

JS API

TypeScript definitions are maintained in types/index.d.ts.

The CFB object exposes the following methods and properties:

CFB.parse(blob) takes a nodejs Buffer or an array of bytes and returns an parsed representation of the data.

CFB.read(blob, opts) wraps parse.

CFB.find(cfb, path) performs a case-insensitive match for the path (or file name, if there are no slashes) and returns an entry object or null if not found.

CFB.write(cfb, opts) generates a file based on the container.

CFB.writeFile(cfb, filename, opts) creates a file with the specified name.

Parse Options

CFB.read takes an options argument. opts.type controls the behavior:

| type | expected input | |------------|:----------------------------------------------------------------| | "base64" | string: Base64 encoding of the file | | "binary" | string: binary string (byte n is data.charCodeAt(n)) | | "buffer" | nodejs Buffer | | "file" | string: path of file that will be read (nodejs only) | | (default) | buffer or array of 8-bit unsigned int (byte n is data[n]) |

Write Options

CFB.write and CFB.writeFile take options argument.

opts.type controls the behavior:

| type | output | |------------|:----------------------------------------------------------------| | "base64" | string: Base64 encoding of the file | | "binary" | string: binary string (byte n is data.charCodeAt(n)) | | "buffer" | nodejs Buffer | | "file" | string: path of file that will be created (nodejs only) | | (default) | buffer if available, array of 8-bit unsigned int otherwise |

opts.fileType controls the output file type:

| fileType | output | |:-------------------|:------------------------| | 'cfb' (default) | CFB container | | 'zip' | ZIP file | | 'mad' | MIME aggregate document |

opts.compression enables DEFLATE compression for ZIP file type.

Utility Functions

The utility functions are available in the CFB.utils object. Functions that accept a name argument strictly deal with absolute file names:

  • .cfb_new(?opts) creates a new container object.
  • .cfb_add(cfb, name, ?content, ?opts) adds a new file to the cfb. Set the option {unsafe:true} to skip existence checks (for bulk additions)
  • .cfb_del(cfb, name) deletes the specified file
  • .cfb_mov(cfb, old_name, new_name) moves the old file to new path and name
  • .use_zlib(require("zlib")) loads a nodejs zlib instance.

By default, the library uses a pure JS inflate/deflate implementation. NodeJS zlib.InflateRaw exposes the number of bytes read in versions after 8.11.0. If a supplied zlib does not support the required features, a warning will be displayed in the console and the pure JS fallback will be used.

Container Object Description

The objects returned by parse and read have the following properties:

  • .FullPaths is an array of the names of all of the streams (files) and storages (directories) in the container. The paths are properly prefixed from the root entry (so the entries are unique)

  • .FileIndex is an array, in the same order as .FullPaths, whose values are objects following the schema:

interface CFBEntry {
  name: string; /** Case-sensitive internal name */
  type: number; /** 1 = dir, 2 = file, 5 = root ; see [MS-CFB] 2.6.1 */
  content: Buffer | number[] | Uint8Array; /** Raw Content */
  ct?: Date; /** Creation Time */
  mt?: Date; /** Modification Time */
  ctype?: String; /** Content-Type (for MAD) */
}

References

  • MS-CFB: Compound File Binary File Format
  • ZIP APPNOTE.TXT: .ZIP File Format Specification
  • RFC1951: https://www.ietf.org/rfc/rfc1951.txt
  • RFC2045: https://www.ietf.org/rfc/rfc2045.txt
  • RFC2557: https://www.ietf.org/rfc/rfc2557.txt

Local Development

Clone the repository and run the following commands from its root:

npm ci
npm run build
npm test

Consumer Smoke Test

npm run test:package packs the library and exercises an isolated consumer using the repository fixture.

Release Checklist

  1. Update the package version, lockfile, generated version fields, and changelog together.
  2. Run the development checks above and audit both npm audit and npm audit --omit=dev.
  3. Use the GitHub publish workflow with its Prod environment to publish the exact CI tarball.
  4. Verify public npm bytes, package identity, provenance, and the immutable GitHub release evidence.

License

Apache-2.0. Original copyright notices and upstream attribution are retained.

Please consult the attached LICENSE file for details. All rights not explicitly granted by the Apache 2.0 License are reserved by the Original Author.

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

Community and Links

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.