ordering-components

v0.0.1-test

Ordering Internal Dashboard For more information about how to use this package see README

Latest version published 2 years ago
License: ISC

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

46 / 100

Security

Security review needed
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
0.0.1-test | 10/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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

Limited

Weekly Downloads (0)

Download trend
GitHub Stars
2
Forks
5
Contributors
20

Direct Usage Popularity

Occasionally

The npm package ordering-components receives a total of 0 downloads a week. As such, we scored ordering-components popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package ordering-components, we found that it has been starred 2 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

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


Embed Package Health Score Badge

package health: 46/100 package health 46/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
2 years ago
Last Commit
17 days ago

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

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
15 Direct
Versions
5
Install Size
1.09 MB
Dist-tags
1
# of Files
332
Maintainers
1
TS Typings
No

ordering-components 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.