olot

PyPI

Is olot safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for olot v0.1.13. Trust score: 65/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)

olot 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.

olot Capabilities & Permissions

What olot 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 olot

Good instructions lead to good results. brin adds olot 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 →

olot Documentation & Source Code

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

Frequently asked questions about olot safety

Weekly Downloads

44.2K

Version

0.1.13

Other Versions

Last Scanned

Feb 10, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is olot Safe? | PyPI Safety Scan - brin