@pgpmjs/core
PGPM Package and Migration Tools
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with long track record; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:@pgsql/types | AI (phantom-deps): @pgsql/types is declared as a peerDependency and used as a type reference; not directly imported at runtime is expected. | ai | |
| phantom-deps | phantom-dep:@pgpmjs/server-utils | AI (phantom-deps): Declared in dependencies; same-org scoped package used indirectly. | ai | |
| phantom-deps | phantom-dep:csv-to-pg | AI (phantom-deps): Declared in dependencies; referenced in config files as expected for this package. | ai | |
| phantom-deps | phantom-dep:@pgpmjs/migrate-client | AI (phantom-deps): Declared in dependencies; same-org scoped package used indirectly. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI/migration tool legitimately shells out; expected pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Extension loader reads package.json from user-supplied dirs; documented plugin pattern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Package is a PostgreSQL migration tool in the @pgpmjs org; no relation to the 'cors' package. | ai |
Versions (showing 100 of 124)
| Version | Deps | Published |
|---|---|---|
| 6.24.0 | 15 / 5 | |
| 6.23.0 | 15 / 5 | |
| 6.22.1 | 15 / 5 | |
| 6.22.0 | 15 / 5 | |
| 6.21.0 | 15 / 5 | |
| 6.20.2 | 15 / 5 | |
| 6.20.1 | 15 / 5 | |
| 6.20.0 | 15 / 5 | |
| 6.19.1 | 15 / 5 | |
| 6.19.0 | 15 / 5 | |
| 6.18.1 | 15 / 5 | |
| 6.18.0 | 15 / 5 | |
| 6.17.1 | 15 / 5 | |
| 6.17.0 | 15 / 5 | |
| 6.16.1 | 15 / 5 | |
| 6.16.0 | 15 / 5 | |
| 6.15.0 | 15 / 5 | |
| 6.14.0 | 15 / 5 | |
| 6.13.0 | 15 / 5 | |
| 6.12.4 | 15 / 5 | |
| 6.12.3 | 16 / 5 | |
| 6.12.2 | 16 / 5 | |
| 6.12.1 | 16 / 5 | |
| 6.12.0 | 16 / 5 | |
| 6.11.1 | 16 / 5 | |
| 6.11.0 | 16 / 5 | |
| 6.10.8 | 16 / 5 | |
| 6.10.7 | 16 / 5 | |
| 6.10.6 | 16 / 5 | |
| 6.10.5 | 16 / 5 | |
| 6.10.4 | 16 / 5 | |
| 6.10.3 | 16 / 5 | |
| 6.10.2 | 16 / 5 | |
| 6.10.1 | 17 / 5 | |
| 6.10.0 | 17 / 5 | |
| 6.9.3 | 17 / 5 | |
| 6.9.1 | 17 / 5 | |
| 6.9.0 | 17 / 5 | |
| 6.8.2 | 17 / 5 | |
| 6.8.1 | 17 / 5 | |
| 6.8.0 | 17 / 5 | |
| 6.7.1 | 17 / 5 | |
| 6.7.0 | 17 / 5 | |
| 6.6.5 | 16 / 5 | |
| 6.6.4 | 16 / 5 | |
| 6.6.3 | 16 / 5 | |
| 6.6.2 | 16 / 5 | |
| 6.4.2 | 16 / 5 | |
| 6.4.1 | 16 / 5 | |
| 6.4.0 | 16 / 5 | |
| 6.3.2 | 16 / 5 | |
| 6.3.1 | 16 / 5 | |
| 6.3.0 | 16 / 5 | |
| 6.2.0 | 16 / 5 | |
| 6.1.0 | 16 / 5 | |
| 6.0.0 | 16 / 5 | |
| 5.2.1 | 16 / 5 | |
| 5.2.0 | 16 / 5 | |
| 5.1.1 | 16 / 5 | |
| 5.1.0 | 16 / 5 | |
| 5.0.1 | 15 / 5 | |
| 5.0.0 | 15 / 5 | |
| 4.17.1 | 15 / 5 | |
| 4.17.0 | 15 / 5 | |
| 4.16.1 | 15 / 5 | |
| 4.16.0 | 15 / 5 | |
| 4.15.1 | 15 / 5 | |
| 4.15.0 | 15 / 5 | |
| 4.14.0 | 15 / 5 | |
| 4.13.3 | 15 / 5 | |
| 4.13.2 | 15 / 5 | |
| 4.13.1 | 15 / 5 | |
| 4.13.0 | 15 / 5 | |
| 4.12.2 | 15 / 5 | |
| 4.12.1 | 15 / 5 | |
| 4.12.0 | 15 / 5 | |
| 4.11.0 | 15 / 5 | |
| 4.10.1 | 15 / 5 | |
| 4.10.0 | 15 / 5 | |
| 4.9.1 | 15 / 5 | |
| 4.9.0 | 15 / 5 | |
| 4.8.0 | 15 / 5 | |
| 4.7.2 | 15 / 5 | |
| 4.7.1 | 15 / 5 | |
| 4.7.0 | 15 / 5 | |
| 4.6.3 | 15 / 5 | |
| 4.6.2 | 15 / 5 | |
| 4.6.1 | 15 / 5 | |
| 4.6.0 | 15 / 5 | |
| 4.5.4 | 15 / 5 | |
| 4.5.3 | 15 / 5 | |
| 4.5.2 | 15 / 5 | |
| 4.5.1 | 15 / 5 | |
| 4.5.0 | 15 / 5 | |
| 4.4.0 | 15 / 5 | |
| 4.3.0 | 15 / 5 | |
| 4.2.1 | 15 / 5 | |
| 4.2.0 | 15 / 5 | |
| 4.1.2 | 15 / 5 | |
| 4.1.1 | 15 / 5 |
v6.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.4
2 findingsPackage name '@pgpmjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
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.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.3
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.2
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.1
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
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.2
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.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.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.