@omegup/msync

npm

Is @omegup/msync safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @omegup/msync 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)

@omegup/msync 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.

@omegup/msync Capabilities & Permissions

What @omegup/msync can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

MONGO_URL

AGENTS.md for @omegup/msync

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

@omegup/msync Documentation & Source Code

For the full @omegup/msync README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @omegup/msync safety

Weekly Downloads

444

Version

0.1.18

Last Scanned

3 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: MONGO_URL

Is @omegup/msync Safe? | npm Safety Scan - brin