alert

foreman

v3.0.1

Node Implementation of Foreman

Unrecognized
Latest version published 3 years ago
    npm install foreman
  

Package Health Score

59 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Recognized
Download trend

Weekly Downloads (62,988)

Dependents
107
GitHub Stars
1.2K
Forks
124
Contributors
30

The npm package foreman receives a total of 62,988 downloads a week. As such, we scored foreman popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package foreman, we found that it has been starred 1,197 times, and that 107 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

04/2014
08/2014
06/2015
08/2016
06/2018

Direct Vulnerabilities

0.3.0
0.4.2
1.4.1
2.0.0
Popular
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.3.0
0.4.2
Popular
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.3.0
  • 0
    H
  • 0
    M
  • 0
    L
0.4.2
  • 0
    H
  • 0
    M
  • 0
    L
1.4.1
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Unrecognized

Security Policy
No

We found a way for you to contribute to the project! Looks like foreman is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test foreman
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
0
Last Release
3 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of foreman 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 foreman 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.

Community

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

With more than 10 contributors for the foreman 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 foreman is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 59/100 package health 59/100

Package

Node.js Compatibility
>=6

Age
9 years
Dependencies
4 Direct
Versions
49
Install Size
61.9 kB
Dist-tags
2
# of Files
27
Maintainers
6
TS Typings
No

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