1. Advisor
  2. JavaScript packages
  3. cssnext

cssnext

v1.8.5

Use tomorrow's CSS syntax, today For more information about how to use this package see README

Latest version published 3 years ago
License: MIT
NPM
GitHub

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

53 / 100

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.8.5 | 09/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.1 | 06/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.6 | 12/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.5.0 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.4 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (2,418)

Download trend
GitHub Stars
5.3K
Forks
189
Contributors
50

Direct Usage Popularity

TOP 30%

The npm package cssnext receives a total of 2,418 downloads a week. As such, we scored cssnext popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package cssnext, we found that it has been starred 5,300 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
50
Funding
Yes

With more than 10 contributors for the cssnext repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
3 years ago
Last Commit
4 months ago

Further analysis of the maintenance status of cssnext 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 cssnext 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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
10 years
Dependencies
35 Direct
Versions
44
Install Size
159 kB
Dist-tags
1
# of Files
126
Maintainers
2
TS Typings
No

cssnext 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.