package-name
npmIs package-name safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for package-name v0.1.0. 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)
package-name 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.
package-name Capabilities & Permissions
What package-name 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.
Filesystem Access
Reads from the filesystem.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for package-name
Good instructions lead to good results. brin adds package-name 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 →
package-name Documentation & Source Code
For the full package-name README, API documentation, and source code, visit the official package registry.
Frequently asked questions about package-name safety
Install (safety-checked)
Weekly Downloads
Version
0.1.0Last Scanned
Trust Score
Capabilities
Connects to: api.jquery.com, blindsignals.com, bugs.jquery.com...
Reads files
Spawns child processes
Accesses: TEMP