ip-matching

v2.1.2

Utilities for IPv4/IPv6 ranges/subnets/masks parsing/matching, string representations, ...

LGPL-3.0-only
Latest version published 1 year ago
    npm install ip-matching
  
We couldn't find any similar packages Browse all packages

Package Health Score

48 / 100

Security

No known security issues
Powered by Snyk
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
2.1.2 | 07/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0 | 01/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.1 | 10/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 08/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.7 | 05/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
License
LGPL-3.0-only
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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test ip-matching
Get started free

Popularity

Small

Weekly Downloads (1,374)

Download trend
Dependents
0
GitHub Stars
9
Forks
1
Contributors
2

Direct Usage Popularity


The npm package ip-matching receives a total of 1,374 downloads a week. As such, we scored ip-matching popularity level to be Small.

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

Community

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
1 year ago
Last Commit
10 months ago

Further analysis of the maintenance status of ip-matching 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 ip-matching 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
not defined

Age
4 years
Dependencies
0 Direct
Versions
16
Install Size
270 kB
Dist-tags
1
# of Files
49
Maintainers
1
TS Typings
Yes

ip-matching 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.