← Home

@juit/pgproxy-cli

This package provides a simple command line interface to run the PGProxy Server.

100
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package publishes via GitHub Actions with SLSA attestation; CI/CD publisher is the expected pattern for this org. ai
provenance slsa-provenance AI (provenance): SLSA provenance via Sigstore CI/CD attestation; stable positive signal for this package. ai
dependencies unvetted-dep:@juit/pgproxy-server AI (dependencies): Same-org monorepo sibling dependency; consistent versioning and clean provenance across releases. ai

Versions (showing 100 of 111)

Version Deps Published
1.4.34 5 / 0
1.4.33 5 / 0
1.4.32 5 / 0
1.4.31 5 / 0
1.4.30 5 / 0
1.4.29 5 / 0
1.4.28 5 / 0
1.4.27 5 / 0
1.4.26 5 / 0
1.4.25 5 / 0
1.4.24 5 / 0
1.4.23 5 / 0
1.4.22 5 / 0
1.4.21 5 / 0
1.4.20 5 / 0
1.4.19 5 / 0
1.4.18 5 / 0
1.4.17 5 / 0
1.4.16 5 / 0
1.4.15 5 / 0
1.4.14 5 / 0
1.4.13 5 / 0
1.4.12 5 / 0
1.4.11 5 / 0
1.4.10 5 / 0
1.4.9 5 / 0
1.4.8 5 / 0
1.4.7 5 / 0
1.4.5 5 / 0
1.4.4 5 / 0
1.4.3 5 / 0
1.4.2 5 / 0
1.4.1 5 / 0
1.4.0 5 / 0
1.3.7 5 / 0
1.3.6 5 / 0
1.3.5 5 / 0
1.3.4 5 / 0
1.3.3 5 / 0
1.3.2 5 / 0
1.3.1 5 / 0
1.3.0 5 / 0
1.2.1 5 / 0
1.2.0 5 / 0
1.1.50 5 / 0
1.1.49 5 / 0
1.1.48 5 / 0
1.1.47 5 / 0
1.1.46 5 / 0
1.1.45 5 / 0
1.1.44 5 / 0
1.1.43 5 / 0
1.1.42 5 / 0
1.1.41 5 / 0
1.1.39 5 / 0
1.1.38 5 / 0
1.1.37 5 / 0
1.1.36 5 / 0
1.1.35 5 / 0
1.1.34 5 / 0
1.1.33 5 / 0
1.1.32 5 / 0
1.1.30 5 / 0
1.1.29 5 / 0
1.1.28 5 / 0
1.1.27 5 / 0
1.1.26 5 / 0
1.1.25 5 / 0
1.1.24 5 / 0
1.1.23 5 / 0
1.1.22 5 / 0
1.1.21 5 / 0
1.1.20 5 / 0
1.1.19 5 / 0
1.1.18 5 / 0
1.1.17 5 / 0
1.1.16 5 / 0
1.1.15 5 / 0
1.1.14 5 / 0
1.1.13 5 / 0
1.1.12 5 / 0
1.1.10 5 / 0
1.1.9 5 / 0
1.1.8 5 / 0
1.1.7 5 / 0
1.1.6 5 / 0
1.1.5 5 / 0
1.1.4 5 / 0
1.1.3 5 / 0
1.1.2 5 / 0
1.1.1 5 / 0
1.1.0 5 / 0
1.0.35 5 / 0
1.0.34 5 / 0
1.0.33 5 / 0
1.0.32 5 / 0
1.0.31 5 / 0
1.0.30 5 / 0
1.0.29 5 / 0
1.0.28 5 / 0
Showing 100 of 111 Next page →

v1.1.34

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.1.33

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.1.32

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.1.30

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.1.29

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.1.28

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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.

v1.1.16

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.1.15

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.1.14

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.1.13

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.1.12

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.1.10

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.1.9

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.1.8

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.1.7

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.1.6

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.1.5

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.1.4

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.1.3

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.1.2

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.1.1

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.1.0

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.35

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.34

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.33

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.32

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.31

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.30

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.29

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.28

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.