libtelegram

npm

Is libtelegram safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for libtelegram v0.1.18. Trust score: 50/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)

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

libtelegram Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

TOKEN

AGENTS.md for libtelegram

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

libtelegram Documentation & Source Code

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

Frequently asked questions about libtelegram safety

Weekly Downloads

23

Version

0.1.18

License

MIT

Last Scanned

4 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Process

Spawns child processes

Environment

Accesses: TOKEN

Is libtelegram Safe? | npm Safety Scan - brin