Gathering detailed insights and metrics for postcss-color-functional-notation
Gathering detailed insights and metrics for postcss-color-functional-notation
Gathering detailed insights and metrics for postcss-color-functional-notation
Gathering detailed insights and metrics for postcss-color-functional-notation
npm install postcss-color-functional-notation
Typescript
Module System
Min. Node Version
Node Version
NPM Version
97.5
Supply Chain
96.9
Quality
88.1
Maintenance
100
Vulnerability
100
License
CSS (43.25%)
JavaScript (30.24%)
TypeScript (22.9%)
HTML (3.03%)
Nunjucks (0.48%)
Shell (0.1%)
Total Downloads
1,517,838,857
Last Day
334,995
Last Week
5,970,198
Last Month
25,398,150
Last Year
291,405,707
MIT-0 License
981 Stars
4,379 Commits
78 Forks
9 Watchers
6 Branches
132 Contributors
Updated on Jun 30, 2025
Minified
Minified + Gzipped
Latest Version
7.0.10
Package Id
postcss-color-functional-notation@7.0.10
Unpacked Size
10.48 kB
Size
3.49 kB
File Count
7
NPM Version
10.9.0
Node Version
22.12.0
Published on
May 27, 2025
Cumulative downloads
Total Downloads
Last Day
-13.2%
334,995
Compared to previous day
Last Week
-9%
5,970,198
Compared to previous week
Last Month
3.5%
25,398,150
Compared to previous month
Last Year
-7.6%
291,405,707
Compared to previous year
npm install postcss-color-functional-notation --save-dev
PostCSS Color Functional Notation lets you use space and slash separated color notation in CSS, following the CSS Color specification.
1:root { 2 --firebrick: rgb(178 34 34); 3 --firebrick-a50: rgb(70% 13.5% 13.5% / 50%); 4 --firebrick-hsl: hsla(0 68% 42%); 5 --firebrick-hsl-a50: hsl(0 68% 42% / 50%); 6} 7 8/* becomes */ 9 10:root { 11 --firebrick: rgb(178, 34, 34); 12 --firebrick-a50: rgba(179, 34, 34, 0.5); 13 --firebrick-hsl: hsl(0, 68%, 42%); 14 --firebrick-hsl-a50: hsla(0, 68%, 42%, 0.5); 15}
Add PostCSS Color Functional Notation to your project:
1npm install postcss postcss-color-functional-notation --save-dev
Use it as a PostCSS plugin:
1const postcss = require('postcss'); 2const postcssColorFunctionalNotation = require('postcss-color-functional-notation'); 3 4postcss([ 5 postcssColorFunctionalNotation(/* pluginOptions */) 6]).process(YOUR_CSS /*, processOptions */);
The preserve
option determines whether the original notation
is preserved. By default, it is not preserved.
1postcssColorFunctionalNotation({ preserve: true })
1:root { 2 --firebrick: rgb(178 34 34); 3 --firebrick-a50: rgb(70% 13.5% 13.5% / 50%); 4 --firebrick-hsl: hsla(0 68% 42%); 5 --firebrick-hsl-a50: hsl(0 68% 42% / 50%); 6} 7 8/* becomes */ 9 10:root { 11 --firebrick: rgb(178, 34, 34); 12 --firebrick-a50: rgba(179, 34, 34, 0.5); 13 --firebrick-hsl: hsl(0, 68%, 42%); 14 --firebrick-hsl: hsla(0 68% 42%); 15 --firebrick-hsl-a50: hsla(0, 68%, 42%, 0.5); 16} 17 18@supports (color: rgb(0 0 0 / 0)) { 19:root { 20 --firebrick: rgb(178 34 34); 21 --firebrick-a50: rgb(70% 13.5% 13.5% / 50%); 22} 23} 24 25@supports (color: hsl(0 0% 0% / 0)) { 26:root { 27 --firebrick-hsl-a50: hsl(0 68% 42% / 50%); 28} 29}
The enableProgressiveCustomProperties
option determines whether the original notation
is wrapped with @supports
when used in Custom Properties. By default, it is enabled.
[!NOTE] We only recommend disabling this when you set
preserve
tofalse
or if you bring your own fix for Custom Properties.
See what the plugin does in its README.
1postcssColorFunctionalNotation({ enableProgressiveCustomProperties: false })
1:root { 2 --firebrick: rgb(178 34 34); 3 --firebrick-a50: rgb(70% 13.5% 13.5% / 50%); 4 --firebrick-hsl: hsla(0 68% 42%); 5 --firebrick-hsl-a50: hsl(0 68% 42% / 50%); 6} 7 8/* becomes */ 9 10:root { 11 --firebrick: rgb(178, 34, 34); 12 --firebrick: rgb(178 34 34); 13 --firebrick-a50: rgba(179, 34, 34, 0.5); 14 --firebrick-a50: rgb(70% 13.5% 13.5% / 50%); 15 --firebrick-hsl: hsl(0, 68%, 42%); 16 --firebrick-hsl: hsla(0 68% 42%); 17 --firebrick-hsl-a50: hsla(0, 68%, 42%, 0.5); 18 --firebrick-hsl-a50: hsl(0 68% 42% / 50%); 19}
Custom properties do not fallback to the previous declaration
No vulnerabilities found.
Reason
30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
no binaries found in the repo
Reason
1 existing vulnerabilities detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
Found 1/24 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More