motion-dom

npm

Is motion-dom safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for motion-dom v12.34.1. Trust score: 60/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)

motion-dom 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.

motion-dom Capabilities & Permissions

What motion-dom 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.

NODE_ENV

AGENTS.md for motion-dom

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

motion-dom Documentation & Source Code

For the full motion-dom README, API documentation, and source code, visit the official package registry.

Frequently asked questions about motion-dom safety

Weekly Downloads

18.3M

Version

12.34.1

License

MIT

Other Versions

Last Scanned

3 days ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: NODE_ENV

Is motion-dom Safe? | npm Safety Scan - brin