← Home

@malloydata/malloy-interfaces

100
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

malloy-lang-usergmadenscullinmtoy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD is confirmed by SLSA provenance attestation; expected for this package going forward. ai
phantom-deps phantom-dep:@creditkarma/thrift-server-core AI (phantom-deps): Used in thrift codegen config, not directly imported at runtime; stable pattern for this package. ai
bogus-package bogus-package AI (bogus-package): Internal interface package in a monorepo; sparse README and no keywords are expected. ai

Versions (showing 100 of 347)

Version Deps Published
0.0.326 1 / 3
0.0.325 1 / 3
0.0.324 1 / 3
0.0.323 1 / 3
0.0.322 1 / 3
0.0.321 1 / 3
0.0.320 1 / 3
0.0.319 1 / 3
0.0.318 1 / 3
0.0.317 1 / 3
0.0.316 1 / 3
0.0.315 1 / 3
0.0.314 1 / 3
0.0.313 1 / 3
0.0.312 1 / 3
0.0.311 1 / 3
0.0.310 1 / 3
0.0.309 1 / 3
0.0.308 1 / 3
0.0.307 1 / 3
0.0.306 1 / 3
0.0.305 1 / 3
0.0.304 1 / 3
0.0.303 1 / 3
0.0.302 1 / 3
0.0.301 1 / 3
0.0.300 1 / 3
0.0.299 1 / 3
0.0.298 1 / 3
0.0.297 1 / 3
0.0.296 1 / 3
0.0.295 1 / 3
0.0.294 1 / 3
0.0.293 1 / 3
0.0.292 1 / 3
0.0.291 1 / 3
0.0.290 1 / 3
0.0.289 1 / 3
0.0.288 1 / 3
0.0.287 1 / 3
0.0.286 1 / 3
0.0.285 1 / 3
0.0.284 1 / 3
0.0.283 1 / 3
0.0.282 1 / 3
0.0.281 1 / 3
0.0.280 1 / 3
0.0.279 1 / 3
0.0.278 1 / 3
0.0.277 1 / 3
0.0.276 1 / 3
0.0.275 1 / 3
0.0.274 1 / 3
0.0.273 1 / 3
0.0.272 1 / 3
0.0.271 1 / 3
0.0.270 1 / 3
0.0.269 1 / 3
0.0.268 1 / 3
0.0.267 1 / 3
0.0.266 1 / 3
0.0.265 1 / 3
0.0.264 1 / 3
0.0.263 1 / 3
0.0.262 1 / 3
0.0.261 1 / 3
0.0.260 1 / 3
0.0.259 1 / 3
0.0.258 1 / 3
0.0.257 1 / 3
0.0.256 1 / 3
0.0.255 1 / 3
0.0.254 1 / 3
0.0.253 1 / 3
0.0.252 1 / 3
0.0.251 1 / 3
0.0.250 1 / 3
0.0.249 1 / 3
0.0.248 1 / 3
0.0.247 1 / 3
0.0.246 1 / 3
0.0.245 1 / 3
0.0.244 1 / 3
0.0.243 1 / 3
0.0.242 1 / 3
0.0.241 1 / 3
0.0.240 1 / 2
0.0.239 1 / 2
0.0.238 1 / 2
0.0.237 1 / 2
0.0.236 0 / 0
0.0.235 0 / 0
0.0.234 0 / 0
0.0.233 0 / 0
0.0.232 0 / 0
0.0.231 0 / 0
0.0.230 0 / 0
0.0.229 0 / 0
0.0.228 0 / 0
0.0.227 0 / 0
Showing 100 of 347 Next page →

v0.0.269

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.268

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.267

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.266

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.265

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.264

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.263

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.262

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.261

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.260

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.259

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.258

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.257

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.256

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.255

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.254

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.253

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.252

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.251

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.250

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.249

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.248

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.247

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.246

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.245

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.244

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.243

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.242

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.241

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.240

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.239

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.238

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.237

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.236

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.235

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.234

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.233

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.232

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.231

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.230

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.229

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.228

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.227

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.