pg-parameters

npm

Is pg-parameters safe to use?

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

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

pg-parameters Capabilities & Permissions

What pg-parameters can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Process Spawning

This package can spawn child processes.

AGENTS.md for pg-parameters

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

pg-parameters Documentation & Source Code

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

Frequently asked questions about pg-parameters safety

Weekly Downloads

18

Version

0.2.3

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

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