okrs

npm

Is okrs safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for okrs v0.1.66. 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)

okrs Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

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.

okrs Capabilities & Permissions

No system capabilities detected for okrs. 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 okrs

Good instructions lead to good results. brin adds okrs documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

okrs Documentation & Source Code

For the full okrs README, API documentation, and source code, visit the official package registry.

Frequently asked questions about okrs safety

Weekly Downloads

72

Version

0.1.66

License

MIT

Last Scanned

3 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is okrs Safe? | npm Safety Scan - brin