@upsetjs/venn.js 2.0.0

Area Proportional Venn and Euler Diagrams

@upsetjs/venn.js@2.0.0 was published on 2024-11-17. Its manifest declares 0 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 @upsetjs/venn.js versions · Permanent reference to 2.0.0 · Latest release

Package specifications

Version2.0.0
License declarationMIT
Published2024-11-17T19:38:29.050Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count2
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size240.11 KiB
Published file count14
Package typemodule
ES module entrybuild/venn.esm.js
Default entrybuild/venn.esm.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies7
Repository stars49
Repository forks2

Install @upsetjs/venn.js 2.0.0

npm install @upsetjs/venn.js@2.0.0
pnpm add @upsetjs/venn.js@2.0.0
yarn add @upsetjs/venn.js@2.0.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review2/10 — Found 1/4 approved changesets -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Security-Policy0/10 — security policy file not 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