rename-component
npmIs rename-component safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for rename-component v1.0.7. Trust score: 55/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)
rename-component Passed Security Checks
No security concerns detected
0
0
2
Install Scripts Detected
This package runs scripts during installation. Review these scripts before installing.
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.
rename-component Capabilities & Permissions
What rename-component can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads and writes to the filesystem.
Process Spawning
This package can spawn child processes.
AGENTS.md for rename-component
Good instructions lead to good results. brin adds rename-component 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 →
rename-component Documentation & Source Code
For the full rename-component README, API documentation, and source code, visit the official package registry.
Frequently asked questions about rename-component safety
Install (safety-checked)
Weekly Downloads
Version
1.0.7License
MITLast Scanned
Trust Score
Install Scripts
This package has install scripts that run automatically:
preinstall, postinstall
Capabilities
Reads & Writes files
Spawns child processes