@sanity/client

npm

Is @sanity/client safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @sanity/client v7.15.0. Trust score: 85/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)

@sanity/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.

@sanity/client Capabilities & Permissions

What @sanity/client 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.

acme.comapi.sanity.ioblog.sanity.studiobugs.webkit.orgbugzilla.mozilla.orgcode.google.comdeveloper.mozilla.orgen.wikipedia.orgexample.comgithub.com+4 more
Protocols: https

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

DEBUGVERCEL_ENVX_SANITY_LINEAGE

AGENTS.md for @sanity/client

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

@sanity/client Documentation & Source Code

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

Frequently asked questions about @sanity/client safety

Weekly Downloads

1.0M

Version

7.15.0

License

MIT

Other Versions

Last Scanned

5 days ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: acme.com, api.sanity.io, blog.sanity.studio...

Process

Spawns child processes

Environment

Accesses: DEBUG, VERCEL_ENV, X_SANITY_LINEAGE

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