fo-test

v0.0.2

The finanacial objects are packaged as NPM and published to npmjs.com

Apache-2.0
Latest version published over 1 year ago
    npm install fo-test
  

Package Health Score

46 / 100
  • Popularity
    Limited
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Limited
Weekly Downloads (3)
Dependents
0
GitHub Stars
14
Forks
11
Contributors
9

The npm package fo-test receives a total of 3 downloads a week. As such, we scored fo-test popularity level to be Limited.

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

0.0.1
0.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.1
0.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.1
0.0.2
  • 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 fo-test is missing a security policy.

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

Maintenance

Inactive
Commit Frequency
Open Issues
7
Merged PR
20
Open PR
0
Last Commit
3 months ago

Further analysis of the maintenance status of fo-test 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 fo-test 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
9
Funding
No
License
Apache-2.0

This project has seen only 10 or less contributors.

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

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
0 Direct / 0 Total
Versions
2
Install Size
12 kB
Dist-tags
1
# of Files
56
Maintainers
1
TS Typings
No

fo-test 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.