jenkins

v1.1.0

Jenkins client For more information about how to use this package see README

Latest version published 9 months 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

64 / 100

Explore Similar Packages

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.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.2 | 06/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.28.1 | 08/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.27.0 | 08/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.20.1 | 11/2017
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

Recognized

Weekly Downloads (29,206)

Download trend
GitHub Stars
356
Forks
85
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package jenkins receives a total of 29,206 downloads a week. As such, we scored jenkins popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package jenkins, we found that it has been starred 356 times.

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
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the jenkins repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like jenkins is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 64/100 package health 64/100

Maintenance

Inactive

Commit Frequency

Open Issues
20
Open PR
2
Last Release
9 months ago
Last Commit
9 months ago

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

We found that jenkins demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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
12 years
Dependencies
1 Direct
Versions
43
Install Size
75.1 kB
Dist-tags
1
# of Files
17
Maintainers
1
TS Typings
Yes

jenkins 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.