pygeofilter

PyPI

Is pygeofilter safe to use?

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

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

pygeofilter Capabilities & Permissions

What pygeofilter can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

.env (r).env (r).env (r).env (r)

Environment Variables

Accesses the following environment variables.

READTHEDOCS

Native Modules

Contains native code that runs outside the JavaScript sandbox.

lxml

AGENTS.md for pygeofilter

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

pygeofilter Documentation & Source Code

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

Frequently asked questions about pygeofilter safety

Weekly Downloads

10.6K

Version

0.3.3

Last Scanned

Feb 11, 2026

Trust Score

80/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Environment

Accesses: READTHEDOCS

Native

Contains native modules

Is pygeofilter Safe? | PyPI Safety Scan - brin