next-intl
npmIs next-intl safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for next-intl v4.8.3. 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)
next-intl 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.
next-intl Capabilities & Permissions
What next-intl can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads and writes to the filesystem.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for next-intl
Good instructions lead to good results. brin adds next-intl 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 →
next-intl Documentation & Source Code
For the full next-intl README, API documentation, and source code, visit the official package registry.
Frequently asked questions about next-intl safety
Install (safety-checked)
Weekly Downloads
Version
4.8.3License
MITOther Versions
Last Scanned
Trust Score
Capabilities
Reads & Writes files
Spawns child processes
Accesses: NODE_ENV, TURBOPACK, _next_intl_trailing_slash