Gathering detailed insights and metrics for postcss-double-position-gradients
Gathering detailed insights and metrics for postcss-double-position-gradients
Gathering detailed insights and metrics for postcss-double-position-gradients
Gathering detailed insights and metrics for postcss-double-position-gradients
npm install postcss-double-position-gradients
Typescript
Module System
Min. Node Version
Node Version
NPM Version
CSS (43.37%)
JavaScript (30.22%)
TypeScript (22.76%)
HTML (3.06%)
Nunjucks (0.48%)
Shell (0.1%)
Total Downloads
1,389,489,131
Last Day
1,006,387
Last Week
4,651,034
Last Month
21,343,104
Last Year
286,384,507
931 Stars
4,164 Commits
73 Forks
11 Watching
3 Branches
131 Contributors
Minified
Minified + Gzipped
Latest Version
6.0.0
Package Id
postcss-double-position-gradients@6.0.0
Unpacked Size
11.50 kB
Size
3.85 kB
File Count
7
NPM Version
10.7.0
Node Version
22.1.0
Publised On
03 Aug 2024
Cumulative downloads
Total Downloads
Last day
-6.7%
1,006,387
Compared to previous day
Last week
-18.4%
4,651,034
Compared to previous week
Last month
5.8%
21,343,104
Compared to previous month
Last year
-13.7%
286,384,507
Compared to previous year
1
PostCSS Double Position Gradients lets you use double-position gradients in CSS, following the CSS Image Values and Replaced Content specification.
1.linear-gradient { 2 background-image: linear-gradient(90deg, black 25% 50%, blue 50% 75%); 3} 4 5.conic-gradient { 6 background-image: conic-gradient(yellowgreen 40%, gold 0deg 75%, #f06 0deg); 7} 8 9/* becomes */ 10 11.linear-gradient { 12 background-image: linear-gradient(90deg, black 25%, black 50%, blue 50%, blue 75%); 13 background-image: linear-gradient(90deg, black 25% 50%, blue 50% 75%); 14} 15 16.conic-gradient { 17 background-image: conic-gradient(yellowgreen 40%, gold 0deg, gold 75%, #f06 0deg); 18 background-image: conic-gradient(yellowgreen 40%, gold 0deg 75%, #f06 0deg); 19}
Add PostCSS Double Position Gradients to your project:
1npm install postcss-double-position-gradients --save-dev
Use PostCSS Double Position Gradients to process your CSS:
1const postcssDoublePositionGradients = require('postcss-double-position-gradients'); 2 3postcssDoublePositionGradients.process(YOUR_CSS /*, processOptions, pluginOptions */);
Or use it as a PostCSS plugin:
1const postcss = require('postcss'); 2const postcssDoublePositionGradients = require('postcss-double-position-gradients'); 3 4postcss([ 5 postcssDoublePositionGradients(/* pluginOptions */) 6]).process(YOUR_CSS /*, processOptions */);
PostCSS Double Position Gradients runs in all Node environments, with special instructions for:
Node | PostCSS CLI | Webpack | Gulp | Grunt |
---|
The preserve
option determines whether the original double-position gradients
should be preserved. By default, double-position gradients are preserved.
1postcssDoublePositionGradients({ preserve: false })
1.linear-gradient { 2 background-image: linear-gradient(90deg, black 25% 50%, blue 50% 75%); 3} 4 5.conic-gradient { 6 background-image: conic-gradient(yellowgreen 40%, gold 0deg 75%, #f06 0deg); 7} 8 9/* becomes */ 10 11.linear-gradient { 12 background-image: linear-gradient(90deg, black 25%, black 50%, blue 50%, blue 75%); 13} 14 15.conic-gradient { 16 background-image: conic-gradient(yellowgreen 40%, gold 0deg, gold 75%, #f06 0deg); 17}
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.
1postcssDoublePositionGradients({ enableProgressiveCustomProperties: false })
1:root { 2 --a-gradient: linear-gradient(90deg, black 25% 50%, blue 50% 75%); 3} 4 5/* becomes */ 6 7:root { 8 --a-gradient: linear-gradient(90deg, black 25%, black 50%, blue 50%, blue 75%); /* will never be used, not even in older browser */ 9 --a-gradient: linear-gradient(90deg, black 25% 50%, blue 50% 75%); 10}
No vulnerabilities found.
Reason
30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
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 0/21 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-02-03
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