pg-logical-replication
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Manual-to-CI/CD provenance transition, not an account compromise indicator. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer was already a listed contributor; trusted publisher track record. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 2 / 10 | |
| 2.5.0 | 2 / 10 | |
| 2.4.0 | 2 / 10 | |
| 2.3.1 | 2 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.1 | 2 / 10 | |
| 2.2.0 | 2 / 10 | |
| 2.1.1 | 2 / 10 | |
| 2.1.0 | 2 / 10 | |
| 2.0.7 | 2 / 10 | |
| 2.0.6 | 2 / 10 | |
| 2.0.5 | 2 / 10 | |
| 2.0.4 | 2 / 10 |
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findingsThis version was published by a different npm account than previous versions on 2024-05-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.