@csstools/css-color-parser 4.1.7

Parse CSS color values

@csstools/css-color-parser@4.1.7 was published on 2026-06-14. Its manifest declares 2 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.19.0.

All @csstools/css-color-parser versions · Permanent reference to 4.1.7 · Latest release

Package specifications

Version4.1.7
License declarationMIT
Published2026-06-14T14:27:38.349Z
Node.js requirement>=20.19.0
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size53.17 KiB
Published file count6
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars1059
Repository forks83

Install @csstools/css-color-parser 4.1.7

npm install @csstools/css-color-parser@4.1.7
pnpm add @csstools/css-color-parser@4.1.7
yarn add @csstools/css-color-parser@4.1.7

Runtime dependencies

Peer requirements

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.

Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Code-Review0/10 — Found 0/24 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness