nforce

v1.12.2

nforce is a REST API wrapper for force.com, database.com, and salesforce.com

MIT
Latest version published 2 years ago
    npm install nforce
  

Package Health Score

51 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Small

Weekly Downloads (6,059)

Dependents
30
GitHub Stars
432
Forks
168
Contributors
40

The npm package nforce receives a total of 6,059 downloads a week. As such, we scored nforce popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package nforce, we found that it has been starred 432 times, and that 30 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

Direct Vulnerabilities

0.10.0
0.8.0
0.9.4
1.11.0
1.12.2
  • 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

Indirect Vulnerabilities

0.10.0
0.8.0
0.9.4
1.11.0
1.12.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.10.0
0.8.0
0.9.4
1.11.0
1.12.2
  • 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
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like nforce 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 && snyk test nforce
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
10
Merged PR
54
Open PR
0
Last Commit
7 months ago

Further analysis of the maintenance status of nforce 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 nforce 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
No
Code of Conduct
No
Contributors
40
Funding
No

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


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Package

Node.js Compatibility
>= 0.12

Age
9 years
Dependencies
4 Direct
Versions
77
Install Size
343 kB
Dist-tags
1
# of Files
82
Maintainers
1
TS Typings
No

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