create-self-signed

v0.0.1-6

HTTPS自签名证书工具,是为了解决启动本地HTTPS服务时,需要创建自签名证书但很繁琐有时候查教材很耗时。它提供命令行调用方式,可以做到一键生成自签名证书并添加到macOS钥匙串,后续通过命令行还可以随时查看和管理证书内容,同时它还提供API接口,可以很方便地集成到命令行工具里。 For more information about how to use this package see README

Latest version published 4 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

42 / 100

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
0.0.1-6 | 04/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (0)

Download trend
GitHub Stars
4
Forks
3
Contributors
4

Direct Usage Popularity


The npm package create-self-signed receives a total of 0 downloads a week. As such, we scored create-self-signed popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package create-self-signed, we found that it has been starred 4 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like create-self-signed is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 42/100 package health 42/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
1
Last Release
4 years ago
Last Commit
1 year ago

Further analysis of the maintenance status of create-self-signed based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for create-self-signed is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
4 years
Dependencies
3 Direct
Versions
7
Install Size
21.4 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

create-self-signed has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.