brin
brin

markdownly.js

npm

Is markdownly.js safe to use?

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

markdownly.js 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.

markdownly.js Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

FORCE_COLORNO_COLOR

AGENTS.md for markdownly.js

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

markdownly.js Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about markdownly.js safety

Weekly Downloads

11

Version

1.6.0

License

BSD-2-Clause

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: FORCE_COLOR, NO_COLOR

Is markdownly.js Safe? | npm Safety Scan - brin