@opentelemetry/semantic-conventions
npmIs @opentelemetry/semantic-conventions safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @opentelemetry/semantic-conventions v1.39.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/semantic-conventions Passed Security Checks
No security concerns detected
0
0
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/semantic-conventions Capabilities & Permissions
What @opentelemetry/semantic-conventions can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Network Access
This package makes network requests.
AGENTS.md for @opentelemetry/semantic-conventions
Good instructions lead to good results. brin adds @opentelemetry/semantic-conventions documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@opentelemetry/semantic-conventions Documentation & Source Code
For the full @opentelemetry/semantic-conventions README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @opentelemetry/semantic-conventions safety
Install (safety-checked)
Weekly Downloads
Version
1.39.0License
Apache-2.0Last Scanned
Trust Score
Capabilities
Connects to: ai.google.dev, aws.amazon.com, azure.microsoft.com...