Use Custom Properties Queries in CSS
78%
Total Score
healthy
Healthy, with a single-contributor maintenance risk and a repository/package identity mismatch.
No build attestation or trusted-publisher provenance is reported, so consumers receive less evidence about how the published artifact was produced. This is a transparency gap rather than evidence of an unsafe release.
One contributor made all 349 commits in the last three months. Organization ownership provides some handoff capacity, but no second recent contributor is shown, leaving a genuine continuity risk.
The repository recorded 349 commits in three months, demonstrating strong activity. However, all activity came from one active maintainer, so the maintenance evidence is concentrated.
The repository name does not match the package name and its README does not mention postcss-custom-properties. Although a monorepo can explain the name mismatch, the missing package reference leaves some uncertainty that this repository directly represents the package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@csstools/utilities Version ^3.0.0 | — | — |
postcss-value-parser Version ^4.2.0 | — | — |
@csstools/css-tokenizer Version ^4.0.2 | — | — |
@csstools/css-parser-algorithms Version ^4.0.2 | — | — |
@csstools/cascade-layer-name-parser Version ^3.0.2 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.