mytms

npm

Is mytms safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for mytms v2023.1027.8396. 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)

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

mytms Capabilities & Permissions

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

element.eleme.iogithub.comjs.foundationlodash.comnpms.iounderscorejs.orgunpkg.comwallstreetcn.comwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for mytms

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

mytms Documentation & Source Code

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

Frequently asked questions about mytms safety

Weekly Downloads

34

Version

2023.1027.8396

License

ISC

Last Scanned

2 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: element.eleme.io, github.com, js.foundation...

Process

Spawns child processes

Is mytms Safe? | npm Safety Scan - brin