@fullcalendar/google-calendar
npmIs @fullcalendar/google-calendar safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @fullcalendar/google-calendar v6.1.20. 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)
@fullcalendar/google-calendar Passed Security Checks
No security concerns detected
0
0
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.
@fullcalendar/google-calendar Capabilities & Permissions
What @fullcalendar/google-calendar 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.
AGENTS.md for @fullcalendar/google-calendar
Good instructions lead to good results. brin adds @fullcalendar/google-calendar documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@fullcalendar/google-calendar Documentation & Source Code
For the full @fullcalendar/google-calendar README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @fullcalendar/google-calendar safety
Install (safety-checked)
Weekly Downloads
Version
6.1.20License
MITLast Scanned
Trust Score
Capabilities
Connects to: fullcalendar.io, www.googleapis.com
Spawns child processes