@effect/sql-drizzle

npm

Is @effect/sql-drizzle safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @effect/sql-drizzle v0.48.1. Trust score: 75/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)

@effect/sql-drizzle 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.

@effect/sql-drizzle Capabilities & Permissions

No system capabilities detected for @effect/sql-drizzle. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for @effect/sql-drizzle

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

@effect/sql-drizzle Documentation & Source Code

For the full @effect/sql-drizzle README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @effect/sql-drizzle safety

Weekly Downloads

25.6K

Version

0.48.1

License

MIT

Last Scanned

6 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is @effect/sql-drizzle Safe? | npm Safety Scan - brin