brin
brin

jsdoc

npm

Is jsdoc safe to use?

The latest brin safety scan flagged jsdoc v4.0.5 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

jsdoc Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • •Can spawn child processes

brin Recommendations

  • →This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add jsdoc to automatically apply these checks before installation.

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.

jsdoc Capabilities & Permissions

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

package.json (rw).env (rw)package.json (rw)/usr/ (rw).env (rw).env (rw).env (rw)package.json (rw)+6 more

Process Spawning

This package can spawn child processes.

AGENTS.md for jsdoc

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

jsdoc Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about jsdoc safety

Weekly Downloads

2.2M

Version

4.0.5

License

Apache-2.0

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is jsdoc Safe? | npm Safety Scan - brin