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