autoprefixer

npm

Is autoprefixer safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for autoprefixer v10.4.24. 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)

autoprefixer 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.

autoprefixer Capabilities & Permissions

What autoprefixer 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.

AUTOPREFIXER_GRID

AGENTS.md for autoprefixer

Good instructions lead to good results. brin adds autoprefixer 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 →

autoprefixer Documentation & Source Code

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

Frequently asked questions about autoprefixer safety

Weekly Downloads

34.5M

Version

10.4.24

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: AUTOPREFIXER_GRID

Is autoprefixer Safe? | npm Safety Scan - brin