View @turf/nearest-point-on… on Snyk Open Source Advisor

Package Health Score

94 / 100

security
No known security issues
popularity
Influential project
maintenance
Healthy
community
Active

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
7.1.0	\|	08/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
7.0.0	\|	06/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.5.0	\|	07/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.1.5	\|	12/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.0.4	\|	11/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

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

Influential project

Weekly Downloads (418,750)

GitHub Stars: 9.32K
Forks: 942
Contributors: 150

Direct Usage Popularity

The npm package @turf/nearest-point-on-line receives a total of 418,750 downloads a week. As such, we scored @turf/nearest-point-on-line popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @turf/nearest-point-on-line, we found that it has been starred 9,322 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: No
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 150
Funding: No

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

How about a good first contribution to this project? It seems that @turf/nearest-point-on-line is missing a README file.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 244
Open PR: 34
Last Release: 3 months ago
Last Commit: 12 days ago

Further analysis of the maintenance status of @turf/nearest-point-on-line based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @turf/nearest-point-on-line demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 7 years
Dependencies: 9 Direct
Versions: 28
Install Size: 33.6 kB
Dist-tags: 2
# of Files: 9
Maintainers: 9
TS Typings: Yes

@turf/nearest-point-on-line 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.

Not sure how to use @turf/nearest-point-on-line?

To help you get started, we've collected the most common ways that @turf/nearest-point-on-line is being used within popular public projects.

Turfjs / turf / packages / turf-line-overlap / index.ts View on Github

// Overlaps already exists - only append last coordinate of segment
                    if (overlapSegment) overlapSegment = concatSegment(overlapSegment, segment);
                    else overlapSegment = segment;
                // Match segments which don't share nodes (Issue #901)
                } else if (
                    (tolerance === 0) ?
                        booleanPointOnLine(coordsSegment[0], match) &amp;&amp; booleanPointOnLine(coordsSegment[1], match) :
                        nearestPointOnLine(match, coordsSegment[0]).properties.dist &lt;= tolerance &amp;&amp;
                        nearestPointOnLine(match, coordsSegment[1]).properties.dist &lt;= tolerance) {
                    doesOverlaps = true;
                    if (overlapSegment) overlapSegment = concatSegment(overlapSegment, segment);
                    else overlapSegment = segment;
                } else if (
                    (tolerance === 0) ?
                        booleanPointOnLine(coordsMatch[0], segment) &amp;&amp; booleanPointOnLine(coordsMatch[1], segment) :
                        nearestPointOnLine(segment, coordsMatch[0]).properties.dist &lt;= tolerance &amp;&amp;
                        nearestPointOnLine(segment, coordsMatch[1]).properties.dist &lt;= tolerance) {
                    // Do not define (doesOverlap = true) since more matches can occur within the same segment
                    // doesOverlaps = true;
                    if (overlapSegment) overlapSegment = concatSegment(overlapSegment, match);
                    else overlapSegment = match;
                }
            }
        });

View more ways to use @turf/nearest-point-on-line

@turf/nearest-point-on-line dependencies

@turf/bearing @turf/destination @turf/distance @turf/helpers @turf/invariant @turf/line-intersect @turf/meta @types/geojson tslib

@turf/nearest-point-on-line development dependencies

@turf/along @turf/length @turf/truncate @types/benchmark @types/tape benchmark load-json-file npm-run-all tape tsup tsx typescript write-json-file

FAQs

What is @turf/nearest-point-on-line?

turf nearest-point-on-line module. Visit Snyk Advisor to see a full health score report for @turf/nearest-point-on-line, including popularity, security, maintenance & community analysis.

Is @turf/nearest-point-on-line popular?

The npm package @turf/nearest-point-on-line receives a total of 418,750 weekly downloads. As such, @turf/nearest-point-on-line popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @turf/nearest-point-on-line well maintained?

We found that @turf/nearest-point-on-line demonstrated a healthy version release cadence and project activity. It has a community of 150 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @turf/nearest-point-on-line safe to use?

The npm package @turf/nearest-point-on-line was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 8 November-2024, at 04:59 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

@turf/nearest-point-on-line

turf nearest-point-on-line module For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (418,750)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use @turf/nearest-point-on-line?

@turf/nearest-point-on-line dependencies

@turf/nearest-point-on-line development dependencies

FAQs

What is @turf/nearest-point-on-line?

Is @turf/nearest-point-on-line popular?

Is @turf/nearest-point-on-line well maintained?

Is @turf/nearest-point-on-line safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (418,750)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @turf/nearest-point-on-line?

@turf/nearest-point-on-line dependencies

@turf/nearest-point-on-line development dependencies

FAQs

What is @turf/nearest-point-on-line?

Is @turf/nearest-point-on-line popular?

Is @turf/nearest-point-on-line well maintained?

Is @turf/nearest-point-on-line safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues