@oclif/plugin-not-found
npmIs @oclif/plugin-not-found safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @oclif/plugin-not-found v3.2.74. Trust score: 75/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)
@oclif/plugin-not-found 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.
@oclif/plugin-not-found Capabilities & Permissions
No system capabilities detected for @oclif/plugin-not-found. 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 @oclif/plugin-not-found
Good instructions lead to good results. brin adds @oclif/plugin-not-found 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 →
@oclif/plugin-not-found Documentation & Source Code
For the full @oclif/plugin-not-found README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @oclif/plugin-not-found safety
Install (safety-checked)
Weekly Downloads
Version
3.2.74License
MITLast Scanned
Trust Score
Capabilities
No special capabilities detected