npm install @parcel/transformer-sass
The npm package @parcel/transformer-sass receives a total of 18,202 downloads a week. As such, we scored @parcel/transformer-sass popularity level to be Popular.
Based on project statistics from the GitHub repository for the npm package @parcel/transformer-sass, we found that it has been starred 37,458 times, and that 1,686 other projects on the ecosystem are dependent on it.
Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.
Snyk detected that the latest version of @parcel/transformer-sass has a security vulnerability.
We highly advise you to review these security issues.
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
We found a way for you to contribute to the project! Looks like @parcel/transformer-sass is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test @parcel/transformer-sass
Further analysis of the maintenance status of @parcel/transformer-sass based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.
An important project maintenance signal to consider for @parcel/transformer-sass is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.
As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.
A good and healthy external contribution signal for @parcel/transformer-sass project, which invites more than one hundred open source maintainers to collaborate on the repository.
We detected a total of 171 direct & transitive dependencies for @parcel/transformer-sass. See the full dependency tree of @parcel/transformer-sass
@parcel/transformer-sass has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.