@probot/get-private-key

v1.1.1

Get private key from a path, environment variables, or a `*.pem` file in the current working directory For more information about how to use this package see README

Latest version published 1 year ago
License: ISC

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

67 / 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
1.1.1 | 07/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 11/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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

Recognized

Weekly Downloads (14,859)

Download trend
Dependents
4
GitHub Stars
4
Forks
12
Contributors
5

Direct Usage Popularity

Occasionally

The npm package @probot/get-private-key receives a total of 14,859 downloads a week. As such, we scored @probot/get-private-key popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @probot/get-private-key, we found that it has been starred 4 times, and that 4 other projects in the ecosystem are dependent on it.

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

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
5
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
1 year ago
Last Commit
5 days ago

Further analysis of the maintenance status of @probot/get-private-key based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for @probot/get-private-key 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
2 Direct
Versions
4
Install Size
15.3 kB
Dist-tags
1
# of Files
9
Maintainers
7
TS Typings
Yes

@probot/get-private-key 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.