@malloydata/db-postgres
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with CI/CD automation; SLSA provenance attestation confirms legitimate build pipeline. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): @types/pg is declared as a runtime dep for type definitions; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of malloydata monorepo; sparse README is expected for internal connector packages. | ai |
Versions (showing 100 of 420)
| Version | Deps | Published |
|---|---|---|
| 0.0.326 | 4 / 0 | |
| 0.0.325 | 4 / 0 | |
| 0.0.324 | 4 / 0 | |
| 0.0.323 | 4 / 0 | |
| 0.0.322 | 4 / 0 | |
| 0.0.321 | 4 / 0 | |
| 0.0.320 | 4 / 0 | |
| 0.0.319 | 4 / 0 | |
| 0.0.318 | 4 / 0 | |
| 0.0.317 | 4 / 0 | |
| 0.0.316 | 4 / 0 | |
| 0.0.315 | 4 / 0 | |
| 0.0.314 | 4 / 0 | |
| 0.0.313 | 4 / 0 | |
| 0.0.312 | 4 / 0 | |
| 0.0.311 | 4 / 0 | |
| 0.0.310 | 4 / 0 | |
| 0.0.309 | 4 / 0 | |
| 0.0.308 | 4 / 0 | |
| 0.0.307 | 4 / 0 | |
| 0.0.306 | 4 / 0 | |
| 0.0.305 | 4 / 0 | |
| 0.0.304 | 4 / 0 | |
| 0.0.303 | 4 / 0 | |
| 0.0.302 | 4 / 0 | |
| 0.0.301 | 4 / 0 | |
| 0.0.300 | 4 / 0 | |
| 0.0.299 | 4 / 0 | |
| 0.0.298 | 4 / 0 | |
| 0.0.297 | 4 / 0 | |
| 0.0.296 | 4 / 0 | |
| 0.0.295 | 4 / 0 | |
| 0.0.294 | 4 / 0 | |
| 0.0.293 | 4 / 0 | |
| 0.0.292 | 4 / 0 | |
| 0.0.291 | 4 / 0 | |
| 0.0.290 | 4 / 0 | |
| 0.0.289 | 4 / 0 | |
| 0.0.288 | 4 / 0 | |
| 0.0.287 | 4 / 0 | |
| 0.0.286 | 4 / 0 | |
| 0.0.285 | 4 / 0 | |
| 0.0.284 | 4 / 0 | |
| 0.0.283 | 4 / 0 | |
| 0.0.282 | 4 / 0 | |
| 0.0.281 | 4 / 0 | |
| 0.0.280 | 4 / 0 | |
| 0.0.279 | 4 / 0 | |
| 0.0.278 | 4 / 0 | |
| 0.0.277 | 4 / 0 | |
| 0.0.276 | 4 / 0 | |
| 0.0.275 | 4 / 0 | |
| 0.0.274 | 4 / 0 | |
| 0.0.273 | 4 / 0 | |
| 0.0.272 | 4 / 0 | |
| 0.0.271 | 4 / 0 | |
| 0.0.270 | 4 / 0 | |
| 0.0.269 | 4 / 0 | |
| 0.0.268 | 4 / 0 | |
| 0.0.267 | 4 / 0 | |
| 0.0.266 | 4 / 0 | |
| 0.0.265 | 4 / 0 | |
| 0.0.264 | 4 / 0 | |
| 0.0.263 | 4 / 0 | |
| 0.0.262 | 4 / 0 | |
| 0.0.261 | 4 / 0 | |
| 0.0.260 | 4 / 0 | |
| 0.0.259 | 4 / 0 | |
| 0.0.258 | 4 / 0 | |
| 0.0.257 | 4 / 0 | |
| 0.0.256 | 4 / 0 | |
| 0.0.255 | 4 / 0 | |
| 0.0.254 | 4 / 0 | |
| 0.0.253 | 4 / 0 | |
| 0.0.252 | 4 / 0 | |
| 0.0.251 | 4 / 0 | |
| 0.0.250 | 4 / 0 | |
| 0.0.249 | 4 / 0 | |
| 0.0.248 | 4 / 0 | |
| 0.0.247 | 4 / 0 | |
| 0.0.246 | 4 / 0 | |
| 0.0.245 | 4 / 0 | |
| 0.0.244 | 4 / 0 | |
| 0.0.243 | 4 / 0 | |
| 0.0.242 | 4 / 0 | |
| 0.0.241 | 4 / 0 | |
| 0.0.240 | 4 / 0 | |
| 0.0.239 | 4 / 0 | |
| 0.0.238 | 4 / 0 | |
| 0.0.236 | 4 / 0 | |
| 0.0.235 | 4 / 0 | |
| 0.0.234 | 4 / 0 | |
| 0.0.233 | 4 / 0 | |
| 0.0.232 | 4 / 0 | |
| 0.0.231 | 4 / 0 | |
| 0.0.230 | 4 / 0 | |
| 0.0.229 | 4 / 0 | |
| 0.0.228 | 4 / 0 | |
| 0.0.227 | 4 / 0 | |
| 0.0.226 | 4 / 0 |
v0.0.269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.268
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.