hokage-41
npmIs hokage-41 safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for hokage-41 v1.0.0. Trust score: 65/100. 1 known CVE, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
hokage-41 Passed Security Checks
No security concerns detected
1
0
0
Risk Indicators
- •MAL-2025-174779: UNKNOWN
hokage-41 CVE Vulnerabilities (1)
Malicious code in hokage-41 (npm)
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.
hokage-41 Capabilities & Permissions
No system capabilities detected for hokage-41. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.
AGENTS.md for hokage-41
Good instructions lead to good results. brin adds hokage-41 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 →
hokage-41 Documentation & Source Code
For the full hokage-41 README, API documentation, and source code, visit the official package registry.
Frequently asked questions about hokage-41 safety
Install (safety-checked)
Weekly Downloads
Version
1.0.0License
ISCLast Scanned
Trust Score
CVEs (1)
Malicious code in hokage-41 (npm)
Capabilities
No special capabilities detected