Option parser with generated usage and commands. 

Option parser with generated usage and commands

harth

nomnom

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

   this.commands = {};  // expected commands

   this.specs = {};     // option specifications

  /* Add a command to the expected commands */

    // facilitates command('name').options().cb().help()

  if (option.choices && option.choices.indexOf(value) == -1) {

     this.print(name + " must be one of: " + option.choices.join(", "), 1);

/* an arg is an item that's actually parsed from the command line

   e.g. "-l", "log.txt", or "--logfile=log.txt" */

      fullRegex = /^\-\-(no\-)?(.+?)(?:=(.+))?$/,

      chars = charMatch && charMatch[1].split("");

  var isValue = str !== undefined && (str === "" || valRegex.test(str));

    value = fullMatch[1] ? false : fullMatch[3];

/* an opt is what's specified by the user in opts hash */

  var strings = (opt.string || "").split(","),

  for (var i = 0; i < strings.length; i++) {

    if (matches = string.match(/^\-([^-])(?:\s+(.*))?$/)) {

    else if (matches = string.match(/^\-\-(.+?)(?:[=\s]+(.+))?$/)) {

  var abbr = opt.abbr || abbr,   // e.g. v from -v

      full = opt.full || full, // e.g. verbose from --verbose

      metavar = opt.metavar || metavar;  // e.g. PATH from '--config=PATH'

      return opt.full == arg || opt.abbr == arg || opt.position == arg

        || opt.name == arg || (opt.list && arg >= opt.position);

  "description": "Option parser with generated usage and commands",

  "author": "Heather Arthur <fayearthur@gmail.com>",

    "test": "./node_modules/.bin/nodeunit test/*.js"

    "url": "http://github.com/harthur/nomnom.git"

nomnom is an option parser for node. It noms your args and gives them back to you in a hash.

      help: 'JSON file with tests to run'

You don't have to specify anything if you don't want to:

var url = opts[0];     // get the first positional arg

var file = opts.file   // see if --file was specified

var verbose = opts.v   // see if -v was specified

var extras = opts._    // get an array of the unmatched, positional args

for [node.js](http://nodejs.org/) and [npm](http://github.com/isaacs/npm):

Nomnom supports args like `-d`, `--debug`, `--no-debug`, `--file=test.txt`, `--file test.txt`, `-f test.txt`, `-xvf`, and positionals. Positionals are arguments that don't fit the `-a` or `--atomic` format and aren't attached to an option.

Values are JSON parsed, so `--debug=true --count=3 --file=log.txt` would give you:

Nomnom supports command-based interfaces (e.g. with git: `git add -p` and `git rebase -i` where `add` and `rebase` are the commands):

      help: "json manifest of tests to run"

Each command generates its own usage message when `-h` or `--help` is specified with the command.

Nomnom prints out a usage message if `--help` or `-h` is an argument. Usage for these options in `test.js`:

If you don't want the option JSON-parsed, specify type `"string"`.

A callback that will be executed as soon as the option is encountered. If the callback returns a string it will print the string and exit:

         return "count must be an integer";

The position of the option if it's a positional argument. If the option should be matched to the first positional arg use position `0`, etc.

Specifies that the option is a list. Appending can be achieved by specifying the arg more than once on the command line:

	node test.js --file=test1.js --file=test2.js

If the option has a `position` and `list` is `true`, all positional args including and after `position` will be appended to the array.

If this is set to `true` and the option isn't in the args, a message will be printed and the program will exit.

A list of the possible values for the option (e.g. `['run', 'test', 'open']`). If the parsed value isn't in the list a message will be printed and the program will exit.

A function that takes the value of the option as entered and returns a new value that will be seen as the value of the option.

`require("nomnom")` will give you the option parser. You can also make an instance of a parser with `require("nomnom")()`. You can chain any of these functions off of a parser:

Add an option specification with the given name:

Add options as a hash keyed by option name, good for a cli with tons of options like [this example](http://github.com/harthur/replace/blob/master/bin/replace.js):

The string that will override the default generated usage message.

Nomnom can't detect the alias used to run your script. You can use `script` to provide the correct name for the usage printout instead of e.g. `node test.js`.

Takes a command name and gives you a command object on which you can chain command options.

Gives a command object that will be used when no command is called.

Parses node's `process.argv` and returns the parsed options hash. You can also provide argv:

var opts = nomnom.parse(["-xvf", "--atomic=true"])

A command is specified with `nomnom.command('name')`. All these functions can be chained on a command:

Add an option specifically for this command.

Add options for this command as a hash of options keyed by name.

A callback that will be called with the parsed options when the command is used.

A help string describing the function of this command.

Override the default generated usage string for this command.

		@@ -463,2 +463,6 @@ var _ = require("underscore"),

		if (option.transform) {
		value = option.transform(value);
		}

		var name = option.name \|\| arg;
		@@ -465,0 +469,0 @@ if (option.choices && option.choices.indexOf(value) == -1) {

		{
		"name": "nomnom",
		"description": "Option parser with generated usage and commands",
		"version": "1.6.2",
		"version": "1.7.0",
		"author": "Heather Arthur <fayearthur@gmail.com>",
		@@ -6,0 +6,0 @@ "scripts": {

		@@ -176,2 +176,6 @@ # nomnom

		#### type

		If you don't want the option JSON-parsed, specify type `"string"`.

		#### callback
		@@ -184,4 +188,5 @@
		callback: function(count) {
		if (count != parseInt(count))
		if (count != parseInt(count)) {
		return "count must be an integer";
		}
		}
		@@ -211,6 +216,15 @@ })

		#### type
		#### transform

		If you don't want the option JSON-parsed, specify type `"string"`.
		A function that takes the value of the option as entered and returns a new value that will be seen as the value of the option.

		```javascript
		nomnom.option('date', {
		abbr: 'd',
		transform: function(timestamp) {
		return new Date(timestamp);
		}
		})
		```

		#### hidden
		@@ -217,0 +231,0 @@

Improved metrics