@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 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 15 / 5 | |
| 4.0.3 | 15 / 5 | |
| 4.0.2 | 15 / 5 | |
| 4.0.1 | 15 / 5 | |
| 4.0.0 | 15 / 5 | |
| 3.2.3 | 15 / 4 | |
| 3.2.2 | 15 / 4 | |
| 3.2.1 | 15 / 4 | |
| 3.2.0 | 15 / 4 | |
| 3.1.4 | 15 / 4 | |
| 3.1.3 | 15 / 4 | |
| 3.1.2 | 15 / 4 | |
| 3.1.1 | 15 / 4 | |
| 3.1.0 | 15 / 4 | |
| 3.0.9 | 15 / 4 | |
| 3.0.8 | 15 / 4 | |
| 3.0.7 | 15 / 4 | |
| 3.0.6 | 16 / 3 | |
| 3.0.5 | 16 / 3 | |
| 3.0.4 | 16 / 3 | |
| 3.0.3 | 16 / 3 | |
| 3.0.2 | 16 / 3 | |
| 3.0.1 | 16 / 3 | |
| 3.0.0 | 16 / 3 |
v4.1.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.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.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.
v3.1.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.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.