</>PackageGraphPackageGraph

node-forge

npmv1.4.0

JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Safe to adopt

Yes — node-forge scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 169 days ago. 3 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 169 days ago. 3 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 1.6 MB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 3 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    (BSD-3-Clause OR GPL-2.0) — 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 node-forge to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

1.6 MB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >= 6.13.0
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the node-forge README.

var forge = require('node-forge');

node-forge vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
node-forgethis page05(BSD-3-Clause OR GPL-2.0)5 months ago
@noble/hashes59.6M1MIT1 day ago
undici158.5M15MIT1 day ago
follow-redirects91.6M2MIT1 day ago
tweetnacl32.2M2Unlicense1 day ago
@mswjs/interceptors20.3M1MIT1 day ago

Dependencies

Declared by node-forge v1.4.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (27)

browserify ^16.5.2commander ^2.20.0cross-env ^5.2.1eslint ^7.27.0eslint-config-digitalbazaar ^2.8.0express ^4.16.2karma ^4.4.1karma-browserify ^7.0.0karma-chrome-launcher ^3.1.0karma-edge-launcher ^0.4.2karma-firefox-launcher ^1.3.0karma-ie-launcher ^1.0.0karma-mocha ^1.3.0karma-mocha-reporter ^2.2.5karma-safari-launcher ^1.0.0karma-sauce-launcher ^2.0.2karma-sourcemap-loader ^0.3.8karma-tap-reporter 0.0.6karma-webpack ^4.0.2mocha ^5.2.0mocha-lcov-reporter ^1.2.0nodejs-websocket ^1.7.1nyc ^15.1.0opts ^1.2.7webpack ^4.44.1webpack-cli ^3.3.12worker-loader ^2.0.0

Used by

Popular packages that depend on node-forge.

Relationship graph

Dependencies (left) and dependents (right) of node-forge.

Frequently installed together

Release history

3 releases in the last two years, typically about 23 days apart.

Recent versions of node-forge
VersionPublishedSizeLicense
1.4.0latest5 months ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.3.39 months ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.3.29 months ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.3.14 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.3.04 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.2.14 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.2.04 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.1.04 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
1.0.04 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.10.06 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.9.26 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.9.17 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.9.07 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.8.57 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)
0.8.47 years ago1.6 MB(BSD-3-Clause OR GPL-2.0)

Overview

node-forge is an npm package that javaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities. It has 5 known dependents in the graph. The latest version is 1.4.0, released under the (BSD-3-Clause OR GPL-2.0) license.

Who should use it

Teams working in the npm ecosystem who need javaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities and value a focused solution.

When not to use it

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

Pros

  • Clear open-source license ((BSD-3-Clause OR GPL-2.0)).

Cons

  • Large dependency tree (27 direct dependencies) increases install size and audit surface.
  • No bundled TypeScript types (may require a separate @types package).

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

Maintainers

Keywords

Frequently asked questions

Should I use node-forge?

Yes — node-forge scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 169 days ago. 3 releases in the last 2 years.

How do I install node-forge?

Run `npm install node-forge` to add node-forge to your npm project.

What license is node-forge released under?

node-forge is distributed under the (BSD-3-Clause OR GPL-2.0) license.

How popular is node-forge?

npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on node-forge.

Is node-forge still maintained?

The most recent release of node-forge (v1.4.0) was published 5 months ago.

Does node-forge run install scripts?

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