@payloadcms/db-postgres
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Config-referenced utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Config-referenced utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:drizzle-kit | AI (phantom-deps): Config-referenced build tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:to-snake-case | AI (phantom-deps): Config-referenced utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:console-table-printer | AI (phantom-deps): Config-referenced utility; stable false positive for this package. | ai |
Versions (showing 100 of 115)
| Version | Deps | Published |
|---|---|---|
| 3.86.0 | 9 / 5 | |
| 3.85.2 | 9 / 5 | |
| 3.85.1 | 9 / 5 | |
| 3.85.0 | 9 / 5 | |
| 3.84.1 | 9 / 5 | |
| 3.84.0 | 9 / 5 | |
| 3.83.0 | 9 / 5 | |
| 3.82.1 | 9 / 5 | |
| 3.82.0 | 9 / 5 | |
| 3.81.0 | 9 / 5 | |
| 3.80.0 | 9 / 5 | |
| 3.79.1 | 9 / 5 | |
| 3.79.0 | 9 / 5 | |
| 3.78.0 | 9 / 5 | |
| 3.77.0 | 9 / 5 | |
| 3.76.1 | 9 / 5 | |
| 3.76.0 | 9 / 5 | |
| 3.75.0 | 9 / 5 | |
| 3.74.0 | 9 / 5 | |
| 3.73.0 | 9 / 5 | |
| 3.72.0 | 9 / 5 | |
| 3.71.1 | 9 / 5 | |
| 3.71.0 | 9 / 5 | |
| 3.70.0 | 9 / 5 | |
| 3.69.0 | 9 / 5 | |
| 3.68.5 | 9 / 5 | |
| 3.68.4 | 9 / 5 | |
| 3.68.3 | 9 / 5 | |
| 3.68.2 | 9 / 5 | |
| 3.68.1 | 9 / 5 | |
| 3.68.0 | 9 / 5 | |
| 3.67.0 | 9 / 5 | |
| 3.66.0 | 9 / 5 | |
| 3.65.0 | 9 / 5 | |
| 3.64.0 | 9 / 5 | |
| 3.63.0 | 9 / 5 | |
| 3.62.1 | 9 / 5 | |
| 3.62.0 | 9 / 5 | |
| 3.61.1 | 9 / 5 | |
| 3.61.0 | 9 / 5 | |
| 3.60.0 | 9 / 5 | |
| 3.59.1 | 9 / 5 | |
| 3.59.0 | 9 / 5 | |
| 3.58.0 | 9 / 5 | |
| 3.57.0 | 9 / 5 | |
| 3.56.0 | 9 / 5 | |
| 3.55.1 | 9 / 5 | |
| 3.55.0 | 9 / 5 | |
| 3.54.0 | 9 / 5 | |
| 3.53.0 | 9 / 5 | |
| 3.52.0 | 9 / 5 | |
| 3.51.0 | 9 / 5 | |
| 3.50.0 | 9 / 5 | |
| 3.49.1 | 9 / 5 | |
| 3.49.0 | 9 / 5 | |
| 3.48.0 | 9 / 5 | |
| 3.47.0 | 9 / 5 | |
| 3.46.0 | 9 / 5 | |
| 3.45.0 | 9 / 5 | |
| 3.44.0 | 9 / 5 | |
| 3.43.0 | 9 / 5 | |
| 3.42.0 | 9 / 5 | |
| 3.41.0 | 9 / 5 | |
| 3.40.0 | 9 / 5 | |
| 3.39.1 | 9 / 5 | |
| 3.39.0 | 9 / 5 | |
| 3.38.0 | 9 / 5 | |
| 3.37.0 | 9 / 5 | |
| 3.36.1 | 9 / 5 | |
| 3.36.0 | 9 / 5 | |
| 3.35.1 | 9 / 5 | |
| 3.35.0 | 9 / 5 | |
| 3.34.0 | 9 / 5 | |
| 3.33.0 | 9 / 5 | |
| 3.32.0 | 9 / 5 | |
| 3.31.0 | 9 / 5 | |
| 3.30.0 | 9 / 5 | |
| 3.29.0 | 9 / 5 | |
| 3.28.1 | 9 / 5 | |
| 3.28.0 | 9 / 5 | |
| 3.27.0 | 9 / 5 | |
| 3.26.0 | 9 / 5 | |
| 3.25.0 | 9 / 5 | |
| 3.24.0 | 9 / 5 | |
| 3.23.0 | 9 / 5 | |
| 3.22.0 | 9 / 5 | |
| 3.21.0 | 9 / 5 | |
| 3.20.0 | 9 / 5 | |
| 3.19.0 | 9 / 5 | |
| 3.18.0 | 9 / 5 | |
| 3.17.1 | 9 / 5 | |
| 3.17.0 | 9 / 5 | |
| 3.16.0 | 9 / 5 | |
| 3.15.1 | 9 / 5 | |
| 3.15.0 | 9 / 5 | |
| 3.14.0 | 9 / 5 | |
| 3.13.0 | 9 / 5 | |
| 3.12.0 | 9 / 5 | |
| 3.11.0 | 9 / 5 | |
| 3.10.0 | 9 / 5 |
v3.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.85.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.