@malloydata/malloy-profiler
This package enables profiling of the Malloy compiler. Currently it only works with stateless compilation of queries. In the future we can extend it to support other kinds of compilation.
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 confirmed by SLSA/Sigstore attestation; legitimate CI/CD migration for this package. | ai | |
| phantom-deps | phantom-dep:clinic | AI (phantom-deps): clinic is used via npm script (npx clinic flame), not imported; phantom-dep is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal tooling package in a monorepo; thin README and no keywords are expected and stable. | ai | |
| provenance | no-provenance | AI (provenance): Malloydata monorepo packages consistently lack provenance; not a risk signal for this publisher. | ai |
Versions (showing 8 of 110)
| Version | Deps | Published |
|---|---|---|
| 0.0.308 | 3 / 0 | |
| 0.0.307 | 3 / 0 | |
| 0.0.306 | 3 / 0 | |
| 0.0.305 | 3 / 0 | |
| 0.0.304 | 3 / 0 | |
| 0.0.303 | 3 / 0 | |
| 0.0.302 | 3 / 0 | |
| 0.0.300 | 3 / 0 |
v0.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.306
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.