brin
brin

sql-pg

npm

Is sql-pg safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for sql-pg v10.4.1. 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)

sql-pg 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.

sql-pg Capabilities & Permissions

What sql-pg 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)/usr/ (r)/usr/ (r).env (r)

Environment Variables

Accesses the following environment variables.

DATABASE_URL

AGENTS.md for sql-pg

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

sql-pg Documentation & Source Code

For the full sql-pg README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about sql-pg safety

Weekly Downloads

63

Version

10.4.1

License

MIT

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Environment

Accesses: DATABASE_URL

Is sql-pg Safe? | npm Safety Scan - brin