marked

npm

Is marked safe to use?

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

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

marked Capabilities & Permissions

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

AGENTS.md for marked

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

marked Documentation & Source Code

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

Frequently asked questions about marked safety

Weekly Downloads

26.6M

Version

17.0.2

License

MIT

Other Versions

Last Scanned

Feb 11, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is marked Safe? | npm Safety Scan - brin