</>PackageGraphPackageGraph

getpass

npmv0.1.7

getpass for node.js

Not recommended for new projects

No — getpass should not be adopted for new projects. Last published 3424 days ago.

  • AAdoption: grade A, Excellent.

    17.6M downloads per week and 1 known dependents.

  • FMaintenance: grade F, Failing.

    Last published 3424 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding getpass to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing getpass, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the getpass README.

javascriptFull README ↗
const mod_getpass = require('getpass');

Dependencies

Declared by getpass v0.1.7. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on getpass.

Relationship graph

Dependencies (left) and dependents (right) of getpass.

assert-plussshpkgetpass
getpass dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 0 days apart.

Recent versions of getpass
VersionPublishedSizeLicense
0.1.7latest9 years agoMIT
0.1.610 years agoMIT
0.1.510 years agoMPL-2.0
0.1.410 years agoMPL-2.0
0.1.310 years agoMPL-2.0
0.1.210 years agoMPL-2.0
0.1.110 years agoMPL-2.0
0.1.010 years agoMPL-2.0

Overview

getpass is an npm package that getpass for node.js. It is extremely widely used, with about 17.6M downloads per week and 1 known dependents in the graph. The latest version is 0.1.7, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need getpass for node.js and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (17.6M weekly downloads).
  • Clear open-source license (MIT).
  • Lean dependency tree (1 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Frequently asked questions

Should I use getpass?

No — getpass should not be adopted for new projects. Last published 3424 days ago.

How do I install getpass?

Run `npm install getpass` to add getpass to your npm project.

How many dependencies does getpass have?

getpass declares 1 direct dependency and pulls in 1 packages in total once its runtime tree is resolved.

What license is getpass released under?

getpass is distributed under the MIT license.

How popular is getpass?

getpass has approximately 17,554,294 downloads per week and 1 known dependent packages.

Is getpass still maintained?

The most recent release of getpass (v0.1.7) was published 9 years ago.

Does getpass run install scripts?

No. getpass does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.