@opentelemetry/instrumentation-mongoose

npm

Is @opentelemetry/instrumentation-mongoose safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @opentelemetry/instrumentation-mongoose v0.58.0. 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)

@opentelemetry/instrumentation-mongoose 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.

@opentelemetry/instrumentation-mongoose Capabilities & Permissions

What @opentelemetry/instrumentation-mongoose 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.

OTEL_SEMCONV_STABILITY_OPT_IN

AGENTS.md for @opentelemetry/instrumentation-mongoose

Good instructions lead to good results. brin adds @opentelemetry/instrumentation-mongoose 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 →

@opentelemetry/instrumentation-mongoose Documentation & Source Code

For the full @opentelemetry/instrumentation-mongoose README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @opentelemetry/instrumentation-mongoose safety

Weekly Downloads

11.6M

Version

0.58.0

License

Apache-2.0

Other Versions

Last Scanned

3 days ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: OTEL_SEMCONV_STABILITY_OPT_IN

Is @opentelemetry/instrumentation-mongoose Safe? | npm Safety Scan - brin