← Home

@juit/pgproxy-types

npm Repository Homepage

This package provides two-way type conversion between PostgreSQL strings and the data types they represent in JavaScript.

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 expected and verifiable. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is core to PostgreSQL bytea parsing; stable false positive for this package. ai

Versions (showing 100 of 111)

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