pgsql-test
pgsql-test offers isolated, role-aware, and rollback-friendly PostgreSQL environments for integration tests — giving developers realistic test coverage without external state pollution
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): DB admin tool legitimately spreads process.env for subprocess pg credentials; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): PostgreSQL test/admin tooling routinely shells out to pg utilities; expected and documented behavior. | ai | |
| phantom-deps | phantom-dep:@launchql/server-utils | AI (phantom-deps): Declared dep used in config/indirect context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pgpmjs/server-utils | AI (phantom-deps): Declared dep used in config files per finding; stable false positive for this package. | ai |
Versions (showing 51 of 130)
| Version | Deps | Published |
|---|---|---|
| 4.16.4 | 9 / 4 | |
| 4.16.3 | 9 / 4 | |
| 4.16.2 | 9 / 4 | |
| 4.16.1 | 9 / 4 | |
| 4.16.0 | 9 / 4 | |
| 4.15.2 | 9 / 4 | |
| 4.15.1 | 9 / 4 | |
| 4.15.0 | 9 / 4 | |
| 4.14.3 | 9 / 4 | |
| 4.14.2 | 9 / 4 | |
| 4.14.1 | 9 / 4 | |
| 4.14.0 | 9 / 4 | |
| 4.13.2 | 9 / 4 | |
| 4.13.1 | 9 / 4 | |
| 4.13.0 | 9 / 4 | |
| 4.12.1 | 9 / 4 | |
| 4.12.0 | 9 / 4 | |
| 4.11.0 | 9 / 4 | |
| 4.10.0 | 9 / 4 | |
| 4.9.5 | 9 / 4 | |
| 4.9.4 | 9 / 4 | |
| 4.9.3 | 9 / 4 | |
| 4.9.2 | 9 / 4 | |
| 4.9.1 | 9 / 4 | |
| 4.9.0 | 9 / 4 | |
| 4.8.1 | 9 / 4 | |
| 4.8.0 | 9 / 4 | |
| 4.7.8 | 9 / 4 | |
| 4.7.7 | 9 / 4 | |
| 4.7.6 | 9 / 4 | |
| 4.7.5 | 9 / 4 | |
| 4.7.4 | 9 / 4 | |
| 4.7.3 | 9 / 4 | |
| 4.7.2 | 9 / 4 | |
| 4.7.1 | 9 / 4 | |
| 4.7.0 | 9 / 4 | |
| 4.6.3 | 9 / 4 | |
| 4.6.1 | 9 / 4 | |
| 4.6.0 | 9 / 4 | |
| 4.5.10 | 9 / 4 | |
| 4.5.9 | 9 / 4 | |
| 4.5.8 | 9 / 4 | |
| 4.5.7 | 9 / 4 | |
| 4.5.6 | 9 / 4 | |
| 4.5.5 | 9 / 4 | |
| 4.5.4 | 9 / 4 | |
| 4.5.3 | 9 / 4 | |
| 4.5.2 | 9 / 4 | |
| 4.3.2 | 9 / 4 | |
| 4.3.1 | 9 / 4 | |
| 4.3.0 | 9 / 4 |
v4.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.