Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Mar 3, 2024 via pnpm

selfsigned 1.9.1

Generate self signed certificates private and public keys
Package summary
Share
10
issues
4
high severity
vulnerability
3
license
1
2
moderate severity
vulnerability
2
4
low severity
vulnerability
3
license
1
2
licenses
1
BSD
1
MIT
Package created
12 Mar 2013
Version published
12 May 2017
Maintainers
2
Total deps
2
Direct deps
1
License
MIT

Issues

10

4 high severity issues

high
Recommendation: Upgrade to version 0.10.0 or later
via: node-forge@0.6.33
Recommendation: Upgrade to version 1.3.0 or later
via: node-forge@0.6.33
Recommendation: Upgrade to version 1.3.0 or later
via: node-forge@0.6.33
Recommendation: Validate that the package complies with your license policy
via: node-forge@0.6.33
Collapse
Expand

2 moderate severity issues

moderate
Recommendation: Upgrade to version 1.3.0 or later
via: node-forge@0.6.33
Recommendation: Upgrade to version 1.0.0 or later
via: node-forge@0.6.33
Collapse
Expand

4 low severity issues

low
Recommendation: Upgrade to version 1.0.0 or later
via: node-forge@0.6.33
Recommendation: Upgrade to version 0.10.0 or later
via: node-forge@0.6.33
Recommendation: Upgrade to version 1.0.0 or later
via: node-forge@0.6.33
Recommendation: Read and validate the license terms
via: node-forge@0.6.33
Collapse
Expand

Licenses

BSD

Invalid
Not OSI Approved
1 Packages, Including:
node-forge@0.6.33

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
selfsigned@1.9.1
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

1
All Dependencies CSV
β“˜ This is a list of selfsigned 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
node-forge0.6.33588.84 kBBSD
prod
4
2
4

Visualizations

Frequently Asked Questions

What does selfsigned do?

Selfsigned is a Node.js package that generates self-signed certificates along with private and public keys, including self-signed x509 certificates. This tool is paramount for testing and development purposes when SSL certificates are required but a CA signed certificate is not necessary.

How do you use selfsigned?

To use selfsigned, first install the package using npm as follows:

npm install selfsigned

After installing, require the package in your JavaScript file. You can then use the generate function in the selfsigned package to create the certificates. Here's a simple usage example in JavaScript:

var selfsigned = require('selfsigned');
var attrs = [{ name: 'commonName', value: 'contoso.com' }];
var pems = selfsigned.generate(attrs, { days: 365 });
console.log(pems)

This will log the private and public keys, along with the certificate. You can also generate the certificates asynchronously as follows:

selfsigned.generate(attrs, { days: 365 }, function (err, pems) {
  console.log(pems)
});

Moreover, you have the option to generate client certificates by setting the clientCertificate option to true:

var pems = selfsigned.generate(null, { clientCertificate: true });
console.log(pems)

If you wish to override the default client CN, you can add another option for clientCertificateCN:

var pems = selfsigned.generate(null, { clientCertificate: true, clientCertificateCN: 'FooBar' });

Where are the selfsigned docs?

For detailed documentation on the selfsigned package and all feature options and capabilities, this link directs to the GitHub repository for the selfsigned npm package. Additionally, for information on configuring certificate attributes, refer to this link provided in the selfsigned readme. As with most npm packages, the readme file on the repository page acts as the core documentation and usage guide.