Gathering detailed insights and metrics for exif-parser
Gathering detailed insights and metrics for exif-parser
Gathering detailed insights and metrics for exif-parser
Gathering detailed insights and metrics for exif-parser
exif-component
Client-side EXIF parser
ts-exif-parser
A typescript library to extract Exif metadata from images, in node and in the browser.
blueimp-load-image
JavaScript Load Image is a library to load images provided as File or Blob objects or via URL. It returns an optionally scaled, cropped or rotated HTML img or canvas element. It also provides methods to parse image metadata to extract IPTC and Exif tags a
get-orientation
Get orientation from image file
A javascript library to extract EXIF metadata from JPEG images, in node and in the browser.
npm install exif-parser
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
219 Stars
95 Commits
53 Forks
11 Watching
1 Branches
11 Contributors
Updated on 15 Oct 2024
JavaScript (98.75%)
Makefile (1.25%)
Cumulative downloads
Total Downloads
Last day
-3%
226,753
Compared to previous day
Last week
3.8%
1,266,158
Compared to previous week
Last month
4.7%
5,224,591
Compared to previous month
Last year
-4.6%
57,019,335
Compared to previous year
2
exif-parser is a parser for image metadata in the exif format, the most popular metadata format for jpeg and tiff images. It is written in pure javascript and has no external dependencies. It can also get the size of jpeg images and the size of the jpeg thumbnail embedded in the exif data. It can also extract the embedded thumbnail image.
npm install exif-parser
You can also build a browser bundle to include it with a <script>
tag in a HTML document, like this:
git clone git@github.com:bwindels/exif-parser.git
cd exif-parser/
make build-browser-bundle
Built versions of the bundles are also available in the exif-parser-browser-bundles repo.
This will generate a dist/exif-parser-(version).js
and dist/exif-parser-(version)-min.js
file. These bundles expose the parser on the ExifParser
global variable, which you would use like this:
var parser = window.ExifParser.create(arrayBuffer);
To start parsing exif data, create a new parser like below. Note that the buffer you pass does not have to be the buffer for the full jpeg file. The exif section of a jpeg file has a maximum size of 65535 bytes and the section seems to always occur within the first 100 bytes of the file. So it is safe to only fetch the first 65635 bytes of a jpeg file and pass those to the parser.
The buffer you pass to create can be a node buffer or a DOM ArrayBuffer.
Note that the parse
method throws an Error when the data passed in is not valid JPEG data.
var parser = require('exif-parser').create(buffer);
try {
var result = parser.parse();
} catch(err) {
// got invalid data, handle error
}
Before calling parse, you can set a number of flags on the parser, telling it how to behave while parsing.
Add fields in the binary format to result. Since these fields are mostly used for internal fields like Padding, you generally are not interested in these. If enabled, values for these fields will be a Buffer object in node or an ArrayBuffer in DOM environments (browsers).
parser.enableBinaryFields([boolean]), default false;
EXIF tags are organized into different sections, and to tell you the offset to other sections, EXIF uses certain tags. These tags don't tell you anything about the image, but are more for parsers to find out about all tags. Hence, these "pointer" fields are not included in the result tags field by default. Change this flag to include them nonetheless.
parser.enablePointers([boolean]), default false;
Resolve tags to their textual name, making result.tags a dictonary object instead of an array with the tag objects with no textual tag name.
parser.enableTagNames([boolean]), default true;
Read the image size while parsing.
parser.enableImageSize([boolean]), default true;
Read the EXIF tags. Could be useful to disable if you only want to read the image size.
parser.enableReturnTags([boolean]), default true;
EXIF values can be represented in a number of formats (fractions, degrees, arrays, ...) with different precision. Enabling this tries to cast values as much as possible to the appropriate javascript types like number, Date.
parser.enableSimpleValues([boolean]), default true;
the tags that were found while parsing are stored in result.tags
unless you set parser.enableReturnTags(false)
. If parser.enableTagNames
is set to true, result.tags
will be an object with the key being the tag name and the value being the tag value. If parser.enableTagNames
is set to false, result.tags
will be an array of objects containing section, type and value properties.
If parser.enableImageSize
is set to true, result.getImageSize()
will give you the image size as an object with width and height properties.
You can check if there is a thumbnail present in the exif data with result.hasThumbnail()
. Exif supports thumbnails is jpeg and tiff format, though most are in jpeg format. You can check if there is a thumbnail present in a give format by passing the mime type: result.hasThumbnail("image/jpeg")
.
You can also get the image size of the thumbnail as an object with width and height properties: result.getThumbnailSize()
.
To get the node buffer or arraybuffer containing just the thumbnail, call result.getThumbnailBuffer()
Install nodeunit
globally from npm if you haven't done so already.
You can run the tests with nodeunit test/test-*.js
.
I welcome external contributions through pull requests. If you do so, please don't use regular expressions. I don't like them, and don't want to maintain a project where they are used. Also, when fixing a bug please provide a regression unit test if it makes sense.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 10/19 approved changesets -- score normalized to 5
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More