@juit/pgproxy-client-node
This package provides a NodeJS specific client for PGProxy Servers.
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 is confirmed by SLSA provenance attestation; legitimate for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with legitimate maintenance; SLSA attestation confirms integrity. | ai |
Versions (showing 100 of 111)
| Version | Deps | Published |
|---|---|---|
| 1.4.34 | 2 / 0 | |
| 1.4.33 | 2 / 0 | |
| 1.4.32 | 2 / 0 | |
| 1.4.31 | 2 / 0 | |
| 1.4.30 | 2 / 0 | |
| 1.4.29 | 2 / 0 | |
| 1.4.28 | 2 / 0 | |
| 1.4.27 | 2 / 0 | |
| 1.4.26 | 2 / 0 | |
| 1.4.25 | 2 / 0 | |
| 1.4.24 | 2 / 0 | |
| 1.4.23 | 2 / 0 | |
| 1.4.22 | 2 / 0 | |
| 1.4.21 | 2 / 0 | |
| 1.4.20 | 2 / 0 | |
| 1.4.19 | 2 / 0 | |
| 1.4.18 | 2 / 0 | |
| 1.4.17 | 2 / 0 | |
| 1.4.16 | 2 / 0 | |
| 1.4.15 | 2 / 0 | |
| 1.4.14 | 2 / 0 | |
| 1.4.13 | 2 / 0 | |
| 1.4.12 | 2 / 0 | |
| 1.4.11 | 2 / 0 | |
| 1.4.10 | 2 / 0 | |
| 1.4.9 | 2 / 0 | |
| 1.4.8 | 2 / 0 | |
| 1.4.7 | 2 / 0 | |
| 1.4.5 | 2 / 0 | |
| 1.4.4 | 2 / 0 | |
| 1.4.3 | 2 / 0 | |
| 1.4.2 | 2 / 0 | |
| 1.4.1 | 2 / 0 | |
| 1.4.0 | 2 / 0 | |
| 1.3.7 | 2 / 0 | |
| 1.3.6 | 2 / 0 | |
| 1.3.5 | 2 / 0 | |
| 1.3.4 | 2 / 0 | |
| 1.3.3 | 2 / 0 | |
| 1.3.2 | 2 / 0 | |
| 1.3.1 | 2 / 0 | |
| 1.3.0 | 2 / 0 | |
| 1.2.1 | 2 / 0 | |
| 1.2.0 | 2 / 0 | |
| 1.1.50 | 2 / 0 | |
| 1.1.49 | 2 / 0 | |
| 1.1.48 | 2 / 0 | |
| 1.1.47 | 2 / 0 | |
| 1.1.46 | 2 / 0 | |
| 1.1.45 | 2 / 0 | |
| 1.1.44 | 2 / 0 | |
| 1.1.43 | 2 / 0 | |
| 1.1.42 | 2 / 0 | |
| 1.1.41 | 2 / 0 | |
| 1.1.39 | 2 / 0 | |
| 1.1.38 | 2 / 0 | |
| 1.1.37 | 2 / 0 | |
| 1.1.36 | 2 / 0 | |
| 1.1.35 | 2 / 0 | |
| 1.1.34 | 2 / 0 | |
| 1.1.33 | 2 / 0 | |
| 1.1.32 | 2 / 0 | |
| 1.1.30 | 2 / 0 | |
| 1.1.29 | 2 / 0 | |
| 1.1.28 | 2 / 0 | |
| 1.1.27 | 2 / 0 | |
| 1.1.26 | 2 / 0 | |
| 1.1.25 | 2 / 0 | |
| 1.1.24 | 2 / 0 | |
| 1.1.23 | 2 / 0 | |
| 1.1.22 | 2 / 0 | |
| 1.1.21 | 2 / 0 | |
| 1.1.20 | 2 / 0 | |
| 1.1.19 | 2 / 0 | |
| 1.1.18 | 2 / 0 | |
| 1.1.17 | 2 / 0 | |
| 1.1.16 | 2 / 0 | |
| 1.1.15 | 2 / 0 | |
| 1.1.14 | 2 / 0 | |
| 1.1.13 | 2 / 0 | |
| 1.1.12 | 2 / 0 | |
| 1.1.10 | 2 / 0 | |
| 1.1.9 | 2 / 0 | |
| 1.1.8 | 2 / 0 | |
| 1.1.7 | 2 / 0 | |
| 1.1.6 | 2 / 0 | |
| 1.1.5 | 2 / 0 | |
| 1.1.4 | 2 / 0 | |
| 1.1.3 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.35 | 2 / 0 | |
| 1.0.34 | 2 / 0 | |
| 1.0.33 | 2 / 0 | |
| 1.0.32 | 2 / 0 | |
| 1.0.31 | 2 / 0 | |
| 1.0.30 | 2 / 0 | |
| 1.0.29 | 2 / 0 | |
| 1.0.28 | 2 / 0 |
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.