postcss-reporter
npmIs postcss-reporter safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for postcss-reporter v7.1.0. Trust score: 75/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-reporter Passed Security Checks
No security concerns detected
0
0
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-reporter Capabilities & Permissions
What postcss-reporter can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Environment Variables
Accesses the following environment variables.
AGENTS.md for postcss-reporter
Good instructions lead to good results. brin adds postcss-reporter documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
postcss-reporter Documentation & Source Code
For the full postcss-reporter README, API documentation, and source code, visit the official package registry.
Frequently asked questions about postcss-reporter safety
Install (safety-checked)
Weekly Downloads
Version
7.1.0License
MITLast Scanned
Trust Score
Capabilities
Accesses: CI, TERM