← Home

node-pg-migrate

npm Repository Homepage
6
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

shinigami92salsita-npmtheo

Keywords

apicockroachcockroachdbdatabasedbdb-migrateexpandableextensiblemigratemigrationmigrationsmigratorpgpostgrepostgrespostgresqlprogramableprogramaticsql

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:node-pg-migrate AI (npm-metadata): Self-referential file:. devDependency, standard pattern; stable FP. ai
provenance missing-githead AI (provenance): Explained by move to CI/CD trusted-publisher with SLSA provenance. ai

Versions (showing 6 of 6)

Version Deps Published
9.0.0 3 / 21
8.0.4 2 / 37
8.0.3 2 / 37
8.0.2 2 / 36
8.0.1 2 / 36
8.0.0 2 / 36

v9.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: shinigami92 → GitHub Actions (on 2026-07-17, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (shinigami92) on 2026-07-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.