postcss-unique-selectors

npm

Is postcss-unique-selectors safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for postcss-unique-selectors v7.0.4. Trust score: 85/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

postcss-unique-selectors Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

postcss-unique-selectors Capabilities & Permissions

No system capabilities detected for postcss-unique-selectors. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for postcss-unique-selectors

Good instructions lead to good results. brin adds postcss-unique-selectors documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

postcss-unique-selectors Documentation & Source Code

For the full postcss-unique-selectors README, API documentation, and source code, visit the official package registry.

Frequently asked questions about postcss-unique-selectors safety

Weekly Downloads

13.6M

Version

7.0.4

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is postcss-unique-selectors Safe? | npm Safety Scan - brin