@csstools/postcss-progressive-custom-properties 3.0.3
Correctly declare progressive enhancements for CSS Custom Properties.
@csstools/postcss-progressive-custom-properties@3.0.3 was published on 2023-12-15. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^14 || ^16 || >=18.
All @csstools/postcss-progressive-custom-properties versions · Permanent reference to 3.0.3 · Latest release
Package specifications
| Version | 3.0.3 |
|---|---|
| License declaration | MIT-0 |
| Published | 2023-12-15T23:17:01.593Z |
| Node.js requirement | ^14 || ^16 || >=18 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 45.97 KiB |
| Published file count | 7 |
| Package type | module |
| ES module entry | dist/index.mjs |
| Default entry | dist/index.cjs |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 1059 |
| Repository forks | 83 |
Install @csstools/postcss-progressive-custom-properties 3.0.3
npm install @csstools/postcss-progressive-custom-properties@3.0.3 pnpm add @csstools/postcss-progressive-custom-properties@3.0.3 yarn add @csstools/postcss-progressive-custom-properties@3.0.3
Runtime dependencies
- postcss-value-parser ^4.2.0
Peer requirements
- postcss ^8.4
Optional dependencies
- None declared
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.
| Maintained | 10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Code-Review | 0/10 — Found 0/24 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 10/10 — security policy file detected |
| Token-Permissions | 9/10 — detected GitHub workflow tokens with excessive permissions |
| License | 10/10 — license file detected |
| Branch-Protection | 3/10 — branch protection is not maximal on development and all release branches |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 9/10 — dependency not pinned by hash detected -- score normalized to 9 |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 10/10 — SAST tool is run on all commits |
Evidence and freshness
- https://registry.npmjs.org/%40csstools%2Fpostcss-progressive-custom-properties/3.0.3 — retrieved 2026-10-31T17:09:57.700Z
- https://api.deps.dev/v3/projects/github.com%2Fcsstools%2Fpostcss-plugins — retrieved 2026-10-31T16:34:32.514Z