</>PackageGraphPackageGraph

buffer-image-size

npmv0.6.4TypeScript

get dimensions of any image buffer

Not recommended for new projects

No — buffer-image-size should not be adopted for new projects. Last published 3115 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 3115 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 2 transitive packages, about 2.6 MB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding buffer-image-size to a project.

1
Direct dependencies

Runtime packages this one declares itself.

2
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

2.6 MB
Install size

Unpacked size of this package plus its entire runtime tree.

2
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing buffer-image-size, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >=4.0
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the buffer-image-size README.

javascriptFull README ↗
var sizeOf = require('buffer-image-size');
var dimensions = sizeOf(yourImageBuffer);
console.log(dimensions.width, dimensions.height);

buffer-image-size vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
buffer-image-sizethis page01MIT8 years ago
image-size01MIT1 day ago
get-east-asian-width69.3M1MIT1 day ago
string-width03MIT1 day ago
@blazediff/core01MIT1 day ago
d3-shape02ISC1 day ago

Dependencies

Declared by buffer-image-size v0.6.4. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

@types/node *

Dev (7)

coveralls ^3.0.0eslint ^4.13.1expect.js ^0.3.1glob ^7.1.1mocha ^4.0.1nyc ^11.2.1sinon ^4.0.2

Used by

Popular packages that depend on buffer-image-size.

happy-domnpm

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML.

↓ 0/wk◈ 6 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of buffer-image-size.

@types/nodehappy-dombuffer-image-size
buffer-image-size dependencies dependents

Frequently installed together

entitiesnpm

Encode & decode XML and HTML entities with ease & speed

↓ 204M/wk◈ 3 dependents⚖ BSD-2-ClauseTS
vitestnpm

Next generation testing framework powered by Vite

↓ 92.7M/wk◈ 129 dependents⚖ MITTS
@vitest/uinpm

UI for Vitest

↓ 8.9M/wk◈ 9 dependents⚖ MITTS
@types/wsnpm

TypeScript definitions for ws

↓ 0/wk◈ 21 dependents⚖ MITTS
whatwg-mimetypenpm

Parses, serializes, and manipulates MIME types, according to the WHATWG MIME Sniffing Standard

↓ 0/wk◈ 3 dependents⚖ MIT
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
@types/whatwg-mimetypenpm

TypeScript definitions for whatwg-mimetype

↓ 0/wk◈ 2 dependents⚖ MITTS
prettiernpm

Prettier is an opinionated code formatter

↓ 114.2M/wk◈ 159 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 0 days apart.

Recent versions of buffer-image-size
VersionPublishedSizeLicense
0.6.4latest8 years ago17 KBMIT
0.6.38 years ago17 KBMIT
0.6.28 years ago16 KBMIT

Overview

buffer-image-size is an npm package that get dimensions of any image buffer. It has 1 known dependents in the graph. The latest version is 0.6.4, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need get dimensions of any image buffer and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

jccr

Keywords

bmpcurdimensionsgifheighticoimagejpegpngpsdresolutionsizesvgwebpwidth

Frequently asked questions

Should I use buffer-image-size?

No — buffer-image-size should not be adopted for new projects. Last published 3115 days ago.

How do I install buffer-image-size?

Run `npm install buffer-image-size` to add buffer-image-size to your npm project.

How many dependencies does buffer-image-size have?

buffer-image-size declares 8 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 2.6 MB on disk.

What license is buffer-image-size released under?

buffer-image-size is distributed under the MIT license.

How popular is buffer-image-size?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on buffer-image-size.

Is buffer-image-size still maintained?

The most recent release of buffer-image-size (v0.6.4) was published 8 years ago.

Does buffer-image-size run install scripts?

No. buffer-image-size does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.