parse-png

npmv2.1.0

Parse a PNG

Not recommended for new projects

No — parse-png should not be adopted for new projects. Last published 2548 days ago.

?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
FMaintenance: grade F, Failing.
Last published 2548 days ago.
AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 3.8 KB installed (at least — some of the tree is still being crawled).
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 parse-png to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

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

3.8 KB

Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Compatibility

Node.js: node >=10
Module format: CommonJS only
TypeScript: No bundled types
Install scripts: None

Quick start

A usage example from the parse-png README.

jsFull README ↗

const fs = require('fs');
const parsePng = require('parse-png');

(async () => {
	const png = await parsePng(fs.readFileSync('unicorn.png'));

	console.log(png);
	/*
	{
		width: 200,
		height: 133,
		depth: 8,
		interlace: false,
		palette: false,

Example truncated — see the full README.

parse-png vs the alternatives

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

Package	Weekly downloads	Dependents	License	Last release
parse-pngthis page	0	1	MIT	7 years ago
p-limit	293.1M	5	MIT	1 day ago
p-locate	216.9M	1	MIT	1 day ago
node-fetch	172.9M	9	MIT	1 day ago
undici	158.5M	15	MIT	1 day ago
axios	106.5M	4	MIT	1 day ago

Dependencies

Declared by parse-png v2.1.0. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

pngjs ^3.3.0

Dev (7)

@types/node ^12.7.5@types/pngjs ^3.3.2ava ^2.4.0file-type ^7.2.0get-stream ^3.0.0tsd ^0.7.4xo ^0.24.0

Used by

Popular packages that depend on parse-png.

@expo/image-utilsnpm

A package used by Expo CLI for processing images

↓ 0/wk◈ 3 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of parse-png.

parse-png dependencies dependents

Frequently installed together

semvernpm

The semantic version parser used by npm.

↓ 0/wk◈ 55 dependents⚖ ISC

@expo/require-utilsnpm

Reusable require and Node resolution utilities library for Expo

↓ 0/wk◈ 6 dependents⚖ MITTS

getenvnpm

Get and typecast environment variables.

↓ 0/wk◈ 7 dependents⚖ MIT

@expo/spawn-asyncnpm

A Promise-based interface into processes created by child_process.spawn

↓ 0/wk◈ 9 dependents⚖ MITTS

jimp-compactnpm

Compact version of Jimp

↓ 0/wk◈ 1 dependents⚖ MITTS

Release history

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

Recent versions of parse-png
Version	Published	Size	License
2.1.0latest	7 years ago	3.8 KB	MIT
2.0.0	7 years ago	3.1 KB	MIT
1.1.2	9 years ago	—	MIT
1.1.1	10 years ago	—	MIT
1.1.0	10 years ago	—	MIT
1.0.0	10 years ago	—	MIT

Overview

parse-png is an npm package that parse a PNG. It has 1 known dependents in the graph. The latest version is 2.1.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need parse a PNG and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

Clear open-source license (MIT).

Cons

No bundled TypeScript types (may require a separate @types package).

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

Maintainers

kevva

Keywords

parse png promise

Frequently asked questions

Should I use parse-png?

No — parse-png should not be adopted for new projects. Last published 2548 days ago.

How do I install parse-png?

Run `npm install parse-png` to add parse-png to your npm project.

How many dependencies does parse-png have?

parse-png declares 8 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 3.8 KB on disk.

What license is parse-png released under?

parse-png is distributed under the MIT license.

How popular is parse-png?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on parse-png.

Is parse-png still maintained?

The most recent release of parse-png (v2.1.0) was published 7 years ago.

Does parse-png run install scripts?

No. parse-png does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.