@juit/pgproxy-client-psql
This package provides a `PGClient` implementation _directly connecting_ to PostgreSQL servers, and not requiring a PGProxy Server to run.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transitioned to GitHub Actions CI/CD publishing with SLSA attestation; stable pattern for this org. | ai |
Versions (showing 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 1.0.27 | 2 / 0 | |
| 1.0.26 | 2 / 0 | |
| 1.0.25 | 2 / 0 | |
| 1.0.24 | 2 / 0 | |
| 1.0.23 | 2 / 0 | |
| 1.0.22 | 2 / 0 | |
| 1.0.21 | 2 / 0 | |
| 1.0.20 | 2 / 0 | |
| 1.0.19 | 2 / 0 | |
| 1.0.18 | 2 / 0 | |
| 1.0.17 | 2 / 0 |
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.