Version 1.0.2
@stackline/is-buffer
Determine if an object is a Buffer
Independent maintenance of is-buffer 2.0.5. Original authors and licenses are retained.
Installation
# Preserve existing imports with an npm alias
npm install is-buffer@npm:@stackline/is-buffer@1.0.2
# Or use the scoped package name in your imports
npm install @stackline/is-buffer@1.0.2Node.js: >=4. Read the compatibility and maintenance notes before migrating.
Usage and API
@stackline/is-buffer
Determine if an object is a Buffer.
Documentation | npm | Issues | Repository
Current package version: 1.0.2
Why this package?
@stackline/is-buffer is the Stackline-maintained distribution of is-buffer@2.0.5. It is an independent continuation of is-buffer; original authors and licenses remain credited below.
Compatibility
| Item | Value |
|---|---|
| Package | @stackline/is-buffer@1.0.2 |
| API target | is-buffer@2.0.5 |
| Supported Node.js | >=4 |
| License | MIT |
| Main entry | index.js |
| Runtime dependencies | none |
Installation
npm install @stackline/is-buffer
Preserve existing imports and plugin resolution with an npm alias:
npm install is-buffer@npm:@stackline/is-buffer
Usage and API reference
is-buffer

Determine if an object is a Buffer (including the browserify Buffer)
Why not use Buffer.isBuffer?
This module lets you check if an object is a Buffer without using Buffer.isBuffer (which includes the whole buffer module in browserify).
It's future-proof and works in node too!
install
npm install @stackline/is-buffer
usage
var isBuffer = require('@stackline/is-buffer')
isBuffer(new Buffer(4)) // true
isBuffer(Buffer.alloc(4)) //true
isBuffer(undefined) // false
isBuffer(null) // false
isBuffer('') // false
isBuffer(true) // false
isBuffer(false) // false
isBuffer(0) // false
isBuffer(1) // false
isBuffer(1.0) // false
isBuffer('string') // false
isBuffer({}) // false
isBuffer(function foo () {}) // false
license
MIT. Copyright (C) Feross Aboukhadijeh.
Credits and original authors
- Original project: is-buffer.
- Feross Aboukhadijeh.
- Stackline maintenance: Alexandro Paixao Marques and Stackline contributors.
Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.
License
MIT. See the license and notice files in the repository.
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.
Upstream issues and maintenance review
Upstream and issue review
Base: feross/is-buffer, npm is-buffer@2.0.5, commit ec4bf3415108e8971375e6717ad63dde752faebf. Full Git history and MIT license are retained. Last npm release: 2020-11-03. This indicates release inactivity, not proof that the upstream is abandoned.
Reviewed the 2026-09-28 collection of 100 most recently updated open and 30 closed issue/PR entries, with PRs excluded: one open issue and three closed issues were available. This is bounded issue triage, not exhaustive historical review.
- #45: module has no initialization side effects. Added
sideEffects: false; CommonJS remains supported and no ESM conversion is required for this metadata. - Closed #28 and #20: old development tool update failures. Replaced wildcard/obsolete browser service tooling with pinned Tape and dependency-free browser-context tests; original Tape cases still run.
- Closed #13: engine changes break compatibility. Retained
node >=4and the unchanged ES5 runtime source.
No confirmed runtime defect was identified in this review. Runtime source remains byte-for-byte identical to the selected upstream commit. Tests cover native Buffers, typed arrays, DataViews, cross-context inputs, and executing the module without a global Buffer. The browser-context check is a VM test, not a claim of a full browser matrix.
Release changes
Changelog
1.0.0 โ 2026-09-28
Initial Stackline maintenance fork of is-buffer 2.0.5. Preserve the API, CommonJS entry, MIT license and Node >=4 engine requirement. Mark the module free of initialization side effects. Pin current test tooling, retain upstream cases and add browser-context/packed-consumer tests. Releases use the exact reviewed GitHub CI tarball with npm provenance and immutable GitHub evidence.
Release files and references
- README.md
- UPSTREAM.md
- CHANGELOG.md
- LICENSE
- NOTICE
- Package and publication metadata
- Full text documentation
Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.