@mapbox/css-sieve
npmIs @mapbox/css-sieve safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @mapbox/css-sieve v0.1.1. 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)
@mapbox/css-sieve 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.
@mapbox/css-sieve Capabilities & Permissions
What @mapbox/css-sieve can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads from the filesystem.
AGENTS.md for @mapbox/css-sieve
Good instructions lead to good results. brin adds @mapbox/css-sieve 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 →
@mapbox/css-sieve Documentation & Source Code
For the full @mapbox/css-sieve README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @mapbox/css-sieve safety
Install (safety-checked)
Weekly Downloads
Version
0.1.1License
MITLast Scanned
Trust Score
Capabilities
Reads files