relianize

v0.0.15

Export Selenium IDE projects into javascript For more information about how to use this package see README

Latest version published 2 years ago
License: Apache-2.0

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

63 / 100

Security

No known security issues
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.15 | 10/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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

Small

Weekly Downloads (0)

Download trend
GitHub Stars
2.79K
Forks
761
Contributors
50

Direct Usage Popularity


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

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

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

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
50
Funding
Yes

With more than 10 contributors for the relianize repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 63/100 package health 63/100

Maintenance

Inactive

Commit Frequency

Open Issues
407
Open PR
10
Last Release
2 years ago
Last Commit
2 months ago

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

Package

Node.js Compatibility
>=8

Age
4 years
Dependencies
2 Direct
Versions
16
Install Size
238 kB
Dist-tags
1
# of Files
31
Maintainers
1
TS Typings
No

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