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

fnout

v1.1.0

Published

Identify the contents of files, executables in particular

Downloads

2

Readme

fnout

MIT licensed js-standard-style Coverage Status Build Status

fnout (file snout) lets you find what the contents of files are: in particular, whether they're executable or not.

Usage

const fnout = require('fnout')

var buf = new Buffer('#!/bin/bash')
fnout(buf).then((res) => {
  // res = {ext: 'sh', mime: 'application/x-sh', linuxExecutable: true, macExecutable: true}
})

fnout.path('path/to/App.dmg').then((res) => {
  // res = {ext: 'dmg', mime: 'application/x-apple-diskimage'}
})

fnout expects a node.js Buffer and returns a Promise which resolves to an object of the following shape:

{
  ext: '', // typical file extension, might be empty,
  mime: '', // mime-type, might fall back to `application/octet-stream`
  macExecutable: true, // truthy if can be executed on OSX
  linuxExecutable: true, // truthy if can be executed on Linux
}

fnout.path takes a path and an optional readHeader function. The readHeader function should take a path and return the first 262 bytes of the file.

Providing your own readHeader function is especially useful if you're not working off the disk, but reading from an archive for example.