Is @csstools/postcss-progressive-custom-properties safe to use?

@csstools/postcss-progressive-custom-properties has no known vulnerabilities on the latest version (5.0.0). DepScope rates its health at 56/100 (high risk).

Does @csstools/postcss-progressive-custom-properties have known vulnerabilities?

No known vulnerabilities on the latest version of @csstools/postcss-progressive-custom-properties.

Is @csstools/postcss-progressive-custom-properties deprecated?

No, @csstools/postcss-progressive-custom-properties is actively maintained. Latest release: 5.0.0 (2026-01-14).

What are alternatives to @csstools/postcss-progressive-custom-properties?

Popular alternatives to @csstools/postcss-progressive-custom-properties in npm include: minimatch, chalk, commander, eslint-visitor-keys, ajv.

What license does @csstools/postcss-progressive-custom-properties use?

@csstools/postcss-progressive-custom-properties is licensed under MIT-0.

@csstools/postcss-progressive-custom-properties

npmv5.0.0

Correctly declare progressive enhancements for CSS Custom Properties.

License MIT-0permissive24 versions3 maintainers1 deps

csstools/postcss-plugins

/ 100

Health

safe to use

@csstools/[email protected] is safe to use (health: 56/100)

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (1)

postcss-value-parser

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@csstools/postcss-progressive-custom-properties