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 🙏

© 2024 – Pkg Stats / Ryan Hefner

file-mime-sniff

v0.0.2

Published

Package for mime sniffing files

Downloads

20

Readme

file-mime-sniff

NPM Package NPM Package Badge Status

This package receives files as base64 encoded strings, then creates a Buffer to read bytes from. With this, you can either specify mime types allowed for the library to validate if the file adheres to them, or simply pass a file so that the library can find possible mime types it might belong to.

This is more effective than simply reading the file extension, as that can be easily masked. Renaming the file extension would pass the checks, whilst reading the file itself doesn't allow for that circumvention.

How to Use

Installation

npm i mime-sniff

Import methods

import { validateBySet, possibleMimeMatches } from "mime-sniff";
import { base64example } from "./sampleFile";

validateBySet({
  fileToAnalyse: base64example,
  validationSet: "text/plain",
});

possibleMimeMatches({
  fileToAnalyse: base64example
})

Import class

There is absolutely no advantage to doing this, but if classes are your thing go ahead.

import { MimeValidator } from "mime-sniff";
import { base64example } from "./sampleFile";
const validator = new MimeValidator();

validator.validateBySet({
  fileToAnalyse: base64example,
  validationSet: "text/plain",
});

validator.possibleMimeMatches({
  fileToAnalyse: base64example
})

Available methods

  • validateBySet - pass a string or array of strings of mime types (eg. ["text/*", "application/pdf"]) and the method will read your file and check if it adheres to one of the mimes you specified. Returns a boolean, can return an array of mime types the file adheres to if returnFullArrayOfMimes is passed.

  • possibleMimeMatches - reads the base64 file and checks it against all the mime types available, returns an array of possible mime types the file adheres to.

  • availableMimes - returns an array of all the mime types the library supports.