@pgsql/types
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (4855 approved, 0 rejected); dormancy likely reflects PG major-version release cadence. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 17.6.2 | 0 / 1 | |
| 17.6.1 | 0 / 1 | |
| 17.6.0 | 0 / 1 | |
| 17.5.4 | 0 / 1 | |
| 17.5.3 | 0 / 1 | |
| 17.5.2 | 0 / 1 | |
| 17.5.1 | 0 / 1 | |
| 17.5.0 | 0 / 1 | |
| 17.4.2 | 0 / 1 | |
| 17.4.1 | 0 / 1 | |
| 17.4.0 | 0 / 1 | |
| 17.1.0 | 0 / 1 | |
| 17.0.0 | 0 / 12 | |
| 16.1.2 | 0 / 1 | |
| 15.1.2 | 0 / 1 | |
| 14.1.2 | 0 / 1 | |
| 13.11.2 | 0 / 1 |
v17.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pyramation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pyramation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pyramation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pyramation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.