xmlToJsonTs

npm

Is xmlToJsonTs safe to use?

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

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

xmlToJsonTs Capabilities & Permissions

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

github.comnodejs.orgtypescriptlang.org>,
Protocols: http, https, udp

Process Spawning

This package can spawn child processes.

AGENTS.md for xmlToJsonTs

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

xmlToJsonTs Documentation & Source Code

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

Frequently asked questions about xmlToJsonTs safety

Weekly Downloads

171

Version

1.0.0

License

MIT

Last Scanned

1 day ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, nodejs.org, typescriptlang.org>,

Process

Spawns child processes

Is xmlToJsonTs Safe? | npm Safety Scan - brin