pgsql-seed
PostgreSQL seeding utilities with pgpm integration - batteries included
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): Spreading process.env into execSync env is standard for passing DB credentials to subprocesses in a DB tooling package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to run database management commands; expected for a PostgreSQL seeding/admin tool. | ai | |
| phantom-deps | phantom-dep:@pgpmjs/server-utils | AI (phantom-deps): @pgpmjs/server-utils is declared as a dependency and referenced in config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 97)
| Version | Deps | Published |
|---|---|---|
| 2.16.4 | 5 / 2 | |
| 2.16.3 | 5 / 2 | |
| 2.16.2 | 5 / 2 | |
| 2.16.1 | 5 / 2 | |
| 2.16.0 | 5 / 2 | |
| 2.15.2 | 5 / 2 | |
| 2.15.1 | 5 / 2 | |
| 2.15.0 | 5 / 2 | |
| 2.14.3 | 5 / 2 | |
| 2.14.2 | 5 / 2 | |
| 2.14.1 | 5 / 2 | |
| 2.14.0 | 5 / 2 | |
| 2.13.1 | 5 / 2 | |
| 2.13.0 | 5 / 2 | |
| 2.12.1 | 5 / 2 | |
| 2.12.0 | 5 / 2 | |
| 2.11.0 | 5 / 2 | |
| 2.10.0 | 5 / 2 | |
| 2.9.5 | 5 / 2 | |
| 2.9.4 | 5 / 2 | |
| 2.9.3 | 5 / 2 | |
| 2.9.2 | 5 / 2 | |
| 2.9.1 | 5 / 2 | |
| 2.9.0 | 5 / 2 | |
| 2.8.1 | 5 / 2 | |
| 2.8.0 | 5 / 2 | |
| 2.7.8 | 5 / 2 | |
| 2.7.7 | 5 / 2 | |
| 2.7.6 | 5 / 2 | |
| 2.7.5 | 5 / 2 | |
| 2.7.4 | 5 / 2 | |
| 2.7.3 | 5 / 2 | |
| 2.7.2 | 5 / 2 | |
| 2.7.1 | 5 / 2 | |
| 2.7.0 | 5 / 2 | |
| 2.6.3 | 5 / 2 | |
| 2.6.1 | 5 / 2 | |
| 2.6.0 | 5 / 2 | |
| 2.5.10 | 5 / 2 | |
| 2.5.9 | 5 / 2 | |
| 2.5.8 | 5 / 2 | |
| 2.5.7 | 5 / 2 | |
| 2.5.6 | 5 / 2 | |
| 2.5.5 | 5 / 2 | |
| 2.5.4 | 5 / 2 | |
| 2.5.3 | 5 / 2 | |
| 2.5.2 | 5 / 2 | |
| 2.3.2 | 5 / 2 | |
| 2.3.1 | 5 / 2 | |
| 2.3.0 | 5 / 2 | |
| 2.2.3 | 5 / 2 |
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.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.0
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.