@docusaurus/plugin-content-blog

npm

Is @docusaurus/plugin-content-blog safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @docusaurus/plugin-content-blog v3.9.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)

@docusaurus/plugin-content-blog 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.

@docusaurus/plugin-content-blog Capabilities & Permissions

What @docusaurus/plugin-content-blog can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

AGENTS.md for @docusaurus/plugin-content-blog

Good instructions lead to good results. brin adds @docusaurus/plugin-content-blog 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 →

@docusaurus/plugin-content-blog Documentation & Source Code

For the full @docusaurus/plugin-content-blog README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @docusaurus/plugin-content-blog safety

Weekly Downloads

662.6K

Version

3.9.2

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is @docusaurus/plugin-content-blog Safe? | npm Safety Scan - brin