@juit/pgproxy-utils Apache-2.0 11 versions

@juit/pgproxy-utils

npm Repository Homepage

This package provides a number of different utilities for developing and testing with `PGProxy`.

11

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pfumagalli

Keywords

databasepgpoolpostgresproxy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Package migrated to GitHub Actions publishing with SLSA provenance; this is the expected publisher going forward.	ai	2026/05/20
phantom-deps	phantom-dep:@juit/pgproxy-persister	AI (phantom-deps): Same-org sibling package declared as dep; phantom-dep false positive for this monorepo package.	ai	2026/05/18
dependencies	unvetted-dep:@juit/pgproxy-types	AI (dependencies): Sibling monorepo package pinned to exact same version; co-released consistently across 120 versions.	ai	2026/05/06
dependencies	unvetted-dep:@juit/pgproxy-client	AI (dependencies): Sibling monorepo package pinned to exact same version; co-released consistently across 120 versions.	ai	2026/05/06

Versions (showing 11 of 111)

Version	Deps	Published
1.0.27	4 / 0	2024-07-26
1.0.26	4 / 0	2024-07-19
1.0.25	4 / 0	2024-07-12
1.0.24	4 / 0	2024-07-05
1.0.23	4 / 0	2024-07-02
1.0.22	4 / 0	2024-06-21
1.0.21	4 / 0	2024-06-14
1.0.20	4 / 0	2024-06-07
1.0.19	4 / 0	2024-05-31
1.0.18	4 / 0	2024-05-24
1.0.17	4 / 0	2024-05-17

v1.0.27

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.