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

@andromeda/mir-da

v0.0.15

Published

Dynamic Security Analysis

Downloads

55

Readme

mir-da

Dynamically analyze JavaScript programs to extract or enforce RWX sets.

mir-da [bfmp] [i=]

File to start analysis from; defaults to index.js if it exists

-h, --help: Output (this) help -V --version: Output version information -v, vv, vvv, --verbosity: Add (multiple) verbosity levels

-d, --depth : Object depth to analyze (default 3) -e, --enforce <f.json>: Run in enforcement mode, where mir enforces access rules in <f.json> -r, --report <f.json>: Run in reporting mode, where mir simply reports on invalid accesses in <f.json> -s, --save <f.json>: File to output resuslts -p, --print [<out, err>]: Stream to output results (defaults to file, see above)

--module-exclude : Comma-separated list of module IDs (absolute fs paths) to be excluded from the analysis --module-include : Comma-separated list of module IDs (absolute fs paths) to be included (assumes module-exclude='') --context-exclude : Comma-separated context starting points to exclude from tracking (for contexts, see below) --context-include : Comma-separated context starting points to include in tracking (assumes context-exclude='') --prop-exclude : Comma-separated property names to exclude from analysis (e.g., 'Promise,toString,escape,setImmediate') --prop-include : Comma-separated property names to include in the analysis (assumes prop-exclude='*')

Contexts are coarse groups of program elements that are tracked, and fall under these categories (can be included in their long or short form):

  • module-locals, m: Module-local names such as 'require'
  • node-globals, n: All Node.js-related globals, such as 'console' and 'process'
  • es-globals, e: All EcmaScript 6 globals names such Math.sin or
  • user-globals, g: User-defined globals accessed with a 'global' prefix, e.g., 'global.y = 3'
  • with-globals, w: User-defined globals accessed without a prefix, e.g., 'y = 3' (expensive to track)