Is Postcss Is Pseudo Class Safe?

Postcss Is Pseudo Class — Nerq Trust Score 76.5/100 (B+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-18.

Yes, Postcss Is Pseudo Class is safe to use. Postcss Is Pseudo Class is a npm package with a Nerq Trust Score of 76.5/100 (B+), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 90/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-18. Machine-readable data (JSON).

Is Postcss Is Pseudo Class safe?

YES — Postcss Is Pseudo Class has a Nerq Trust Score of 76.5/100 (B+). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → Postcss Is Pseudo Class Privacy Report →

What is Postcss Is Pseudo Class's trust score?

Postcss Is Pseudo Class has a Nerq Trust Score of 76.5/100, earning a B+ grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
90

What are the key security findings for Postcss Is Pseudo Class?

Postcss Is Pseudo Class's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 90/100 — community adoption

What is Postcss Is Pseudo Class and who maintains it?

Authorjonathantneal
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@tanstack/virtual-file-routes (86)@portabletext/react (86)@smithy/protocol-http (86)@smithy/config-resolver (86)@smithy/hash-node (86)
See all safest Npm →

Compare

Postcss Is Pseudo Class vs @tanstack/virtual-file-routesPostcss Is Pseudo Class vs @portabletext/reactPostcss Is Pseudo Class vs @smithy/protocol-http

Safety Guide: Postcss Is Pseudo Class

What is Postcss Is Pseudo Class?

Postcss Is Pseudo Class is a Node.js package — A pseudo-class for matching elements in a selector list.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@csstools/postcss-is-pseudo-class

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Postcss Is Pseudo Class has a Nerq Trust Score of 76/100 (B+) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Postcss Is Pseudo Class Safe?
Yes, it is safe to use. @csstools/postcss-is-pseudo-class with a Nerq Trust Score of 76.5/100 (B+). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (90/100).
What is Postcss Is Pseudo Class's trust score?
@csstools/postcss-is-pseudo-class: 76.5/100 (B+). Score based on Security (90/100), Popularity (90/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@csstools/postcss-is-pseudo-class
What are safer alternatives to Postcss Is Pseudo Class?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @csstools/postcss-is-pseudo-class scores 76.5/100.
Does Postcss Is Pseudo Class have known vulnerabilities?
Nerq checks Postcss Is Pseudo Class against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Postcss Is Pseudo Class actively maintained?
Postcss Is Pseudo Class maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy