xliff

npm

Is xliff safe to use?

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

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

xliff Capabilities & Permissions

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

Network Access

This package makes network requests.

bugzilla.mozilla.orgdeveloper.mozilla.orgdocs.oasis-open.orgen.wikipedia.orgfeross.orgfeross.org>github.commathiasbynens.bemths.bestackoverflow.com+1 more
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for xliff

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

xliff Documentation & Source Code

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

Frequently asked questions about xliff safety

Weekly Downloads

79.1K

Version

6.3.0

License

MIT

Last Scanned

22 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: bugzilla.mozilla.org, developer.mozilla.org, docs.oasis-open.org...

Process

Spawns child processes

Is xliff Safe? | npm Safety Scan - brin