node-vibrant 4.0.1

Extract prominent colors from an image. Supports both node and browser environment.

node-vibrant@4.0.1 was published on 2025-01-13. Its manifest declares 6 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 node-vibrant versions · Permanent reference to 4.0.1 · View npm registry JSON · Latest release

Package specifications

Version4.0.1
License declarationMIT
Published2025-01-13T11:46:24.999Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size19.86 KiB
Published file count63
Package typemodule
ES module entrydist/esm/throw.js
Default entrydist/cjs/throw.cjs
Side effects declarationtrue
Direct advisories0
Resolved graph dependencies62
Repository stars2455
Repository forks115

Install node-vibrant 4.0.1

npm install node-vibrant@4.0.1
pnpm add node-vibrant@4.0.1
yarn add node-vibrant@4.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 1 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review1/10 — Found 2/20 approved changesets -- score normalized to 1
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
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
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness