@malloydata/malloy
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:url | AI (phantom-deps): Likely used indirectly via bundled/transpiled build; established package with no malicious behavior. | ai | |
| phantom-deps | phantom-dep:blueimp-md5 | AI (phantom-deps): Likely used indirectly via bundled/transpiled build; established package with no malicious behavior. | ai | |
| npm-metadata | url-dep:@malloydata/malloy | AI (npm-metadata): Self-referential file: dep, likely monorepo build artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@malloydata/malloy | AI (phantom-deps): Same-scope self-reference, benign. | ai | |
| dependencies | unvetted-dep:antlr4ts | AI (dependencies): antlr4ts is the standard ANTLR4 TypeScript runtime; expected dependency for a query language compiler like Malloy. | ai | |
| phantom-deps | phantom-dep:assert | AI (phantom-deps): Referenced in config/test files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jest-diff | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai |
Versions (showing 51 of 421)
| Version | Deps | Published |
|---|---|---|
| 0.0.426 | 10 / 5 | |
| 0.0.425 | 10 / 5 | |
| 0.0.424 | 10 / 5 | |
| 0.0.423 | 10 / 5 | |
| 0.0.422 | 10 / 5 | |
| 0.0.421 | 10 / 5 | |
| 0.0.420 | 10 / 5 | |
| 0.0.419 | 10 / 5 | |
| 0.0.418 | 10 / 5 | |
| 0.0.417 | 10 / 5 | |
| 0.0.416 | 10 / 5 | |
| 0.0.415 | 11 / 4 | |
| 0.0.414 | 11 / 4 | |
| 0.0.413 | 11 / 4 | |
| 0.0.412 | 11 / 4 | |
| 0.0.411 | 11 / 4 | |
| 0.0.410 | 11 / 4 | |
| 0.0.409 | 11 / 4 | |
| 0.0.408 | 11 / 4 | |
| 0.0.407 | 11 / 4 | |
| 0.0.406 | 11 / 4 | |
| 0.0.405 | 11 / 4 | |
| 0.0.404 | 11 / 4 | |
| 0.0.403 | 11 / 4 | |
| 0.0.402 | 11 / 4 | |
| 0.0.401 | 11 / 4 | |
| 0.0.400 | 11 / 4 | |
| 0.0.399 | 11 / 4 | |
| 0.0.398 | 11 / 4 | |
| 0.0.397 | 11 / 4 | |
| 0.0.396 | 11 / 4 | |
| 0.0.395 | 11 / 4 | |
| 0.0.394 | 11 / 4 | |
| 0.0.393 | 11 / 4 | |
| 0.0.392 | 11 / 4 | |
| 0.0.391 | 11 / 4 | |
| 0.0.390 | 11 / 4 | |
| 0.0.389 | 11 / 4 | |
| 0.0.388 | 11 / 4 | |
| 0.0.387 | 11 / 4 | |
| 0.0.386 | 11 / 4 | |
| 0.0.385 | 11 / 4 | |
| 0.0.384 | 11 / 4 | |
| 0.0.383 | 11 / 4 | |
| 0.0.382 | 11 / 4 | |
| 0.0.381 | 11 / 4 | |
| 0.0.380 | 11 / 4 | |
| 0.0.379 | 11 / 4 | |
| 0.0.378 | 11 / 4 | |
| 0.0.377 | 11 / 4 | |
| 0.0.376 | 11 / 4 |
v0.0.426
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.425
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.424
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.423
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.422
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.421
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.420
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.419
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.418
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.417
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.416
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.415
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.414
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.413
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.412
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.411
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.410
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.409
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.408
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.407
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.406
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.405
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.404
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.403
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.402
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.401
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.400
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.399
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.398
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.397
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.389
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.385
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.384
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.381
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.380
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.379
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.378
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.376
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.