pgpm
PostgreSQL Package Manager - Database migration and package management CLI
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@launchql/server-utils | AI (phantom-deps): Config-file reference only; stable false positive for this CLI package. | ai | |
| dependencies | unvetted-dep:@launchql/env | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/core | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/types | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/logger | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/server | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/explorer | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/templatizer | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@launchql/server-utils | AI (dependencies): Same org/publisher as pgpm; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:find-and-require-package-json | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:appstash | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:yanse | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:pgsql-deparser | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:shelljs | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI deploy tool legitimately uses child_process for executing database/system commands. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env is standard for passing environment variables to child processes in a deployment CLI. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): pgpm is a distinct PostgreSQL package manager CLI, not a typosquat of pg. | ai |
Versions (showing 89 of 194)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 16 / 10 | |
| 4.2.0 | 16 / 10 | |
| 4.1.0 | 16 / 10 | |
| 4.0.1 | 16 / 10 | |
| 4.0.0 | 16 / 10 | |
| 3.3.2 | 16 / 10 | |
| 3.3.1 | 16 / 10 | |
| 3.3.0 | 16 / 10 | |
| 3.2.1 | 16 / 10 | |
| 3.2.0 | 16 / 10 | |
| 3.1.1 | 16 / 10 | |
| 3.1.0 | 16 / 10 | |
| 3.0.1 | 16 / 10 | |
| 3.0.0 | 16 / 10 | |
| 2.12.1 | 16 / 10 | |
| 2.12.0 | 16 / 10 | |
| 2.11.1 | 17 / 11 | |
| 2.11.0 | 17 / 11 | |
| 2.10.15 | 17 / 11 | |
| 2.10.14 | 17 / 11 | |
| 2.10.13 | 17 / 11 | |
| 2.10.11 | 17 / 11 | |
| 2.10.10 | 17 / 11 | |
| 2.10.9 | 17 / 11 | |
| 2.10.8 | 17 / 11 | |
| 2.10.7 | 17 / 11 | |
| 2.10.6 | 17 / 11 | |
| 2.10.5 | 17 / 11 | |
| 2.10.4 | 17 / 11 | |
| 2.10.3 | 17 / 11 | |
| 2.10.2 | 17 / 11 | |
| 2.10.1 | 17 / 11 | |
| 2.10.0 | 16 / 11 | |
| 2.9.1 | 16 / 11 | |
| 2.9.0 | 16 / 11 | |
| 2.8.0 | 16 / 11 | |
| 2.7.11 | 16 / 11 | |
| 2.7.10 | 16 / 11 | |
| 2.7.9 | 16 / 11 | |
| 2.7.8 | 16 / 11 | |
| 2.7.7 | 16 / 11 | |
| 2.7.6 | 16 / 11 | |
| 2.7.5 | 16 / 11 | |
| 2.7.4 | 16 / 11 | |
| 2.7.3 | 16 / 11 | |
| 2.7.2 | 16 / 11 | |
| 2.7.1 | 16 / 11 | |
| 2.7.0 | 16 / 11 | |
| 2.6.0 | 16 / 11 | |
| 2.5.1 | 16 / 11 | |
| 2.5.0 | 16 / 11 | |
| 2.4.1 | 15 / 11 | |
| 2.4.0 | 15 / 11 | |
| 2.3.0 | 15 / 11 | |
| 2.2.1 | 15 / 10 | |
| 2.2.0 | 15 / 10 | |
| 2.1.2 | 15 / 10 | |
| 2.1.1 | 15 / 10 | |
| 2.1.0 | 15 / 10 | |
| 2.0.0 | 15 / 10 | |
| 1.4.2 | 15 / 10 | |
| 1.4.1 | 15 / 10 | |
| 1.4.0 | 15 / 10 | |
| 1.3.0 | 15 / 10 | |
| 1.2.2 | 15 / 10 | |
| 1.2.1 | 15 / 10 | |
| 1.2.0 | 15 / 10 | |
| 1.1.5 | 15 / 10 | |
| 1.1.4 | 15 / 10 | |
| 1.1.3 | 15 / 10 | |
| 1.1.2 | 15 / 10 | |
| 1.1.1 | 15 / 10 | |
| 1.1.0 | 15 / 10 | |
| 1.0.6 | 15 / 10 | |
| 1.0.5 | 15 / 10 | |
| 1.0.4 | 15 / 10 | |
| 1.0.3 | 15 / 10 | |
| 1.0.2 | 15 / 10 | |
| 1.0.1 | 15 / 10 | |
| 1.0.0 | 15 / 10 | |
| 0.6.1 | 15 / 10 | |
| 0.6.0 | 15 / 10 | |
| 0.5.1 | 15 / 10 | |
| 0.5.0 | 15 / 10 | |
| 0.2.13 | 12 / 9 | |
| 0.2.11 | 12 / 9 | |
| 0.2.5 | 12 / 9 | |
| 0.2.4 | 12 / 9 | |
| 0.0.1 | 15 / 9 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.