@spatial/nearest-point

v2.0.0

turf nearest-point module

MIT
Latest version published 2 years ago
    npm install @spatial/nearest-point
  

Package Health Score

73 / 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.0.0 | 09/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.5 | 08/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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 @spatial/nearest-point
Get started free

Popularity

Small

Weekly Downloads (5)

Download trend
Dependents
59
GitHub Stars
7.02K
Forks
801
Contributors
130

Direct Usage Popularity


The npm package @spatial/nearest-point receives a total of 5 downloads a week. As such, we scored @spatial/nearest-point popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @spatial/nearest-point, we found that it has been starred 7,017 times, and that 59 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

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
130
Funding
No

A good and healthy external contribution signal for @spatial/nearest-point project, which invites more than one hundred open source maintainers to collaborate on the repository.


Embed Package Health Score Badge

package health: 73/100 package health 73/100

Maintenance

Inactive

Commit Frequency

Open Issues
218
Open PR
20
Last Release
2 years ago
Last Commit
2 months ago

Further analysis of the maintenance status of @spatial/nearest-point 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 @spatial/nearest-point 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
3 years
Dependencies
4 Direct
Versions
5
Install Size
10 kB
Dist-tags
1
# of Files
7
Maintainers
2
TS Typings
Yes

@spatial/nearest-point 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.