vue-notifications

npm

Is vue-notifications safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for vue-notifications v1.0.3. Trust score: 65/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)

vue-notifications 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.

vue-notifications Capabilities & Permissions

What vue-notifications 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.

lunrjs.complus.google.comservice.weibo.comtwitter.comvkontakte.ruwww.facebook.comwww.instapaper.com
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for vue-notifications

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

vue-notifications Documentation & Source Code

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

Frequently asked questions about vue-notifications safety

Weekly Downloads

1.8K

Version

1.0.3

License

MIT

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: lunrjs.com, plus.google.com, service.weibo.com...

Process

Spawns child processes