parameter

v3.6.0

A parameter verify tools.

MIT
Latest version published 3 years ago
    npm install parameter
  

Package Health Score

59 / 100

Popularity

Recognized

Weekly Downloads (12,639)

Download trend
Dependents
51
GitHub Stars
674
Forks
96
Contributors
20

Direct Usage Popularity

TOP 30%

The npm package parameter receives a total of 12,639 downloads a week. As such, we scored parameter popularity level to be Recognized.

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

09/2015
09/2015
08/2018
12/2018
05/2019

Direct Vulnerabilities

1.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.4.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.5.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.6.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.4.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.5.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.6.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.1.1
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
2.4.0
  • 0
    H
  • 0
    M
  • 0
    L
3.5.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.6.0
  • 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 parameter 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 parameter
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
28
Open PR
9
Last Release
3 years ago
Last Commit
2 years ago

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

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


Embed Package Health Score Badge

package health: 59/100 package health 59/100

Package

Node.js Compatibility
>= 4.0.0

Age
9 years
Dependencies
0 Direct
Versions
29
Install Size
44.7 kB
Dist-tags
1
# of Files
6
Maintainers
4
TS Typings
No

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