sweepline-intersections

A module to check if a polygon self-intersects using a sweepline algorithm

sweepline-intersections@2.0.1 was published on 2024-11-24. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All sweepline-intersections versions · Permanent reference to 2.0.1 · View npm registry JSON

Package specifications

Version2.0.1
License declarationMIT
Published2024-11-24T08:35:40.938Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size101.04 KiB
Published file count10
Package typemodule
ES module entrydist/sweeplineIntersections.esm.js
Default entrydist/sweeplineIntersections.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies272
Repository stars76
Repository forks5

Install sweepline-intersections 2.0.1

npm install sweepline-intersections@2.0.1
pnpm add sweepline-intersections@2.0.1
yarn add sweepline-intersections@2.0.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review2/10 — Found 4/20 approved changesets -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness