@fxhash/gql-client

npm

Is @fxhash/gql-client safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @fxhash/gql-client v0.0.5. 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)

@fxhash/gql-client 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.

@fxhash/gql-client Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

HASURA_ADMIN_SECRET

AGENTS.md for @fxhash/gql-client

Good instructions lead to good results. brin adds @fxhash/gql-client 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 →

@fxhash/gql-client Documentation & Source Code

For the full @fxhash/gql-client README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @fxhash/gql-client safety

Weekly Downloads

9

Version

0.0.5

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: HASURA_ADMIN_SECRET

Is @fxhash/gql-client Safe? | npm Safety Scan - brin