Gathering detailed insights and metrics for postcss-scss
Gathering detailed insights and metrics for postcss-scss
Installations
npm install postcss-scssReleases
Unable to fetch releases
Developer
postcss
Developer Guide
BETA
Module System
CommonJS, ESM
Min. Node Version
>=12.0
Typescript Support
Yes
Node Version
20.7.0
NPM Version
10.1.0
Statistics
657 Stars
258 Commits
33 Forks
17 Watching
1 Branches
29 Contributors
Updated on 06 Oct 2024
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
857,073,121
Last day
-3.8%
803,607
Compared to previous day
Last week
0.4%
4,187,350
Compared to previous week
Last month
8.8%
17,712,081
Compared to previous month
Last year
8.8%
193,077,212
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
Versions
PostCSS SCSS Syntax
This module does not compile SCSS. It simply parses mixins as custom at-rules & variables as properties, so that PostCSS plugins can then transform SCSS source code alongside CSS.
Install
1npm --save install postcss postcss-scss
Usage
There are two ways to use this parser:
1. SCSS Transformations
The main use case of this plugin is to apply PostCSS transformations directly to SCSS source code.
For example, you can lint SCSS source with Stylelint and linter will automatically fix issues in the source.
1// postcss.config.js 2module.exports = { 3 syntax: 'postcss-scss', 4 plugins: { 5 … 6 } 7}
2. Inline Comments for PostCSS
Also you can use this parser just to add // single-line comment
to your PostCSS project (without any Sass):
1:root { 2 // Main theme color 3 --color: red; 4}
Note that you don’t need a special stringifier to handle the output; the default one will automatically convert single line comments into block comments.
1// postcss.config.js 2module.exports = { 3 parser: 'postcss-scss', 4 plugins: { 5 … 6 } 7}
If you want Sass behaviour with removing inline comments, you can use postcss-strip-inline-comments plugin.
Security Contact
To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:8
- Info: no jobLevel write permissions found
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
2 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Reason
Found 4/29 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:63: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:65: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:71: update your workflow using https://app.stepsecurity.io/secureworkflow/postcss/postcss-scss/test.yml/main?enable=pin
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 5 are checked with a SAST tool
Score
4.3
/10
Last Scanned on 2024-11-18
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