brin
brin

postcss

npm

Is postcss safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for postcss v8.5.6. Trust score: 65/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 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 Capabilities & Permissions

What postcss can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Writes to the filesystem.

.env (r).env (r).env (r).env (r).env (r).env (r)/home/ (r)/home/ (r)

Environment Variables

Accesses the following environment variables.

LANGNODE_DISABLE_COLORSNODE_ENV

AGENTS.md for postcss

Good instructions lead to good results. brin adds postcss 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 Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about postcss safety

Weekly Downloads

124.6M

Version

8.5.6

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files

Environment

Accesses: LANG, NODE_DISABLE_COLORS, NODE_ENV