@ecvbdx/js-to-markdown

npm

Is @ecvbdx/js-to-markdown safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @ecvbdx/js-to-markdown v0.0.5. Trust score: 55/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)

@ecvbdx/js-to-markdown 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.

@ecvbdx/js-to-markdown Capabilities & Permissions

What @ecvbdx/js-to-markdown 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.

/usr/ (rw)node_modules (rw)/usr/ (rw)/usr/ (rw)node_modules (rw)

AGENTS.md for @ecvbdx/js-to-markdown

Good instructions lead to good results. brin adds @ecvbdx/js-to-markdown 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 →

@ecvbdx/js-to-markdown Documentation & Source Code

For the full @ecvbdx/js-to-markdown README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @ecvbdx/js-to-markdown safety

Weekly Downloads

6

Version

0.0.5

Last Scanned

3 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Is @ecvbdx/js-to-markdown Safe? | npm Safety Scan - brin