@furystack/odata-fetchr

npm

Is @furystack/odata-fetchr safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @furystack/odata-fetchr v1.0.10. 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)

@furystack/odata-fetchr 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.

@furystack/odata-fetchr Capabilities & Permissions

What @furystack/odata-fetchr can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

Protocols: http

Process Spawning

This package can spawn child processes.

AGENTS.md for @furystack/odata-fetchr

Good instructions lead to good results. brin adds @furystack/odata-fetchr 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 →

@furystack/odata-fetchr Documentation & Source Code

For the full @furystack/odata-fetchr README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @furystack/odata-fetchr safety

Weekly Downloads

76

Version

1.0.10

License

GPL-2.0

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Process

Spawns child processes

Is @furystack/odata-fetchr Safe? | npm Safety Scan - brin