@juit/pgproxy-pool
This package provides low-level connectivity and a connection pool implementation to connect to PosgreSQL databases using `libpq`.
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): Transition from personal account to GitHub Actions CI/CD with SLSA attestation; legitimate automation pattern for this org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @juit/libpq is a same-org first-party dependency, expected for this PostgreSQL proxy package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 1.0.27 | 1 / 0 | |
| 1.0.26 | 1 / 0 | |
| 1.0.25 | 1 / 0 | |
| 1.0.24 | 1 / 0 | |
| 1.0.23 | 1 / 0 | |
| 1.0.22 | 1 / 0 | |
| 1.0.21 | 1 / 0 | |
| 1.0.20 | 1 / 0 | |
| 1.0.19 | 1 / 0 | |
| 1.0.18 | 1 / 0 | |
| 1.0.17 | 1 / 0 |
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.