pg-seed
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 used to run DB admin 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 runtime dep and referenced in config; phantom-dep heuristic false positive. | ai | |
| dependencies | unvetted-dep:pg-copy-streams | AI (dependencies): pg-copy-streams is a legitimate, widely-used PostgreSQL COPY streaming library; its use here is expected and appropriate. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 3 / 3 | |
| 0.14.2 | 3 / 3 | |
| 0.14.1 | 3 / 3 | |
| 0.14.0 | 3 / 3 | |
| 0.13.1 | 3 / 3 | |
| 0.13.0 | 3 / 3 | |
| 0.12.0 | 3 / 3 | |
| 0.11.0 | 3 / 3 | |
| 0.10.0 | 3 / 3 | |
| 0.9.0 | 3 / 3 | |
| 0.8.2 | 3 / 3 | |
| 0.8.1 | 3 / 3 | |
| 0.8.0 | 3 / 3 | |
| 0.7.3 | 3 / 3 | |
| 0.7.2 | 3 / 3 | |
| 0.5.1 | 3 / 3 | |
| 0.5.0 | 3 / 3 | |
| 0.4.0 | 3 / 3 | |
| 0.3.1 | 3 / 3 | |
| 0.3.0 | 3 / 3 | |
| 0.2.2 | 3 / 3 | |
| 0.2.1 | 3 / 3 | |
| 0.2.0 | 3 / 3 | |
| 0.0.1 | 10 / 0 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/constructive-io/constructive/blob/9b68e2d19937ad4e2a81a5de110a197a8572e3d9/admin.js#L34 32 | (0, child_process_1.execSync)(command, { 33 | stdio: this.verbose ? 'inherit' : 'pipe', > 34 | env: { 35 | ...process.env, 36 | ...this.getEnv()
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/constructive-io/constructive/blob/9b68e2d19937ad4e2a81a5de110a197a8572e3d9/esm/admin.js#L31 29 | execSync(command, { 30 | stdio: this.verbose ? 'inherit' : 'pipe', > 31 | env: { 32 | ...process.env, 33 | ...this.getEnv()
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.