foreman

v3.0.1

Node Implementation of Foreman

MIT
Latest version published over 2 years ago
    npm install foreman
  

Explore Similar Packages

Package Health Score

65 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Recognized
Weekly Downloads (80,427)
Dependents
105
GitHub Stars
1.18K
Forks
124
Contributors
20

The npm package foreman receives a total of 80,427 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,178 times, and that 105 other projects on 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

Security and license risk for recent versions


Direct Vulnerabilities

2.0.0-0
2.0.0-1
2.0.0
3.0.0
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

2.0.0-0
2.0.0-1
2.0.0
3.0.0
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

2.0.0-0
2.0.0-1
2.0.0
3.0.0
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

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

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

    # Install the Snyk CLI and test your project
npm i snyk && snyk test foreman
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
1
Merged PR
42
Open PR
0
Last Commit
2 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.

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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No
License
MIT

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.

Package

Node.js Compatibility
>=6

Age
8 years
Dependencies
4 Direct / 7 Total
Versions
5
Install Size
61.9 kB
Dist-tags
2
# of Files
27
Maintainers
12
TS Typings
No

We detected a total of 7 direct & transitive dependencies for foreman. See the full dependency tree of foreman

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.