@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 100 of 421)
| Version | Deps | Published |
|---|---|---|
| 0.0.225 | 6 / 3 | |
| 0.0.224 | 6 / 3 | |
| 0.0.223 | 6 / 3 | |
| 0.0.222 | 6 / 3 | |
| 0.0.221 | 6 / 3 | |
| 0.0.220 | 6 / 3 | |
| 0.0.219 | 6 / 3 | |
| 0.0.218 | 6 / 3 | |
| 0.0.217 | 6 / 3 | |
| 0.0.216 | 6 / 3 | |
| 0.0.215 | 6 / 3 | |
| 0.0.214 | 6 / 3 | |
| 0.0.213 | 6 / 3 | |
| 0.0.212 | 6 / 3 | |
| 0.0.211 | 6 / 3 | |
| 0.0.210 | 6 / 3 | |
| 0.0.209 | 6 / 3 | |
| 0.0.208 | 6 / 3 | |
| 0.0.207 | 6 / 3 | |
| 0.0.206 | 6 / 3 | |
| 0.0.205 | 6 / 3 | |
| 0.0.204 | 6 / 3 | |
| 0.0.203 | 6 / 3 | |
| 0.0.202 | 6 / 3 | |
| 0.0.201 | 6 / 3 | |
| 0.0.200 | 6 / 3 | |
| 0.0.199 | 6 / 3 | |
| 0.0.198 | 6 / 3 | |
| 0.0.197 | 6 / 3 | |
| 0.0.196 | 6 / 3 | |
| 0.0.195 | 6 / 3 | |
| 0.0.194 | 6 / 3 | |
| 0.0.193 | 6 / 3 | |
| 0.0.192 | 6 / 3 | |
| 0.0.191 | 6 / 3 | |
| 0.0.190 | 6 / 3 | |
| 0.0.189 | 6 / 3 | |
| 0.0.188 | 6 / 3 | |
| 0.0.187 | 6 / 3 | |
| 0.0.186 | 6 / 3 | |
| 0.0.185 | 6 / 3 | |
| 0.0.184 | 6 / 3 | |
| 0.0.183 | 6 / 3 | |
| 0.0.182 | 6 / 3 | |
| 0.0.181 | 6 / 3 | |
| 0.0.180 | 6 / 3 | |
| 0.0.179 | 6 / 3 | |
| 0.0.178 | 6 / 3 | |
| 0.0.177 | 6 / 3 | |
| 0.0.176 | 6 / 3 | |
| 0.0.175 | 6 / 3 | |
| 0.0.174 | 6 / 3 | |
| 0.0.173 | 6 / 3 | |
| 0.0.172 | 7 / 3 | |
| 0.0.171 | 7 / 3 | |
| 0.0.170 | 7 / 3 | |
| 0.0.169 | 6 / 3 | |
| 0.0.168 | 6 / 3 | |
| 0.0.167 | 6 / 3 | |
| 0.0.166 | 6 / 3 | |
| 0.0.165 | 6 / 3 | |
| 0.0.164 | 6 / 3 | |
| 0.0.163 | 6 / 3 | |
| 0.0.162 | 6 / 3 | |
| 0.0.161 | 6 / 3 | |
| 0.0.160 | 6 / 3 | |
| 0.0.159 | 6 / 3 | |
| 0.0.158 | 6 / 3 | |
| 0.0.157 | 6 / 3 | |
| 0.0.156 | 6 / 3 | |
| 0.0.155 | 6 / 3 | |
| 0.0.154 | 6 / 3 | |
| 0.0.153 | 6 / 3 | |
| 0.0.152 | 6 / 3 | |
| 0.0.151 | 6 / 3 | |
| 0.0.150 | 6 / 3 | |
| 0.0.149 | 6 / 3 | |
| 0.0.148 | 6 / 3 | |
| 0.0.147 | 6 / 3 | |
| 0.0.146 | 6 / 3 | |
| 0.0.145 | 6 / 3 | |
| 0.0.144 | 6 / 3 | |
| 0.0.143 | 6 / 3 | |
| 0.0.142 | 6 / 3 | |
| 0.0.141 | 6 / 3 | |
| 0.0.140 | 6 / 3 | |
| 0.0.138 | 6 / 3 | |
| 0.0.137 | 6 / 3 | |
| 0.0.136 | 6 / 3 | |
| 0.0.135 | 6 / 3 | |
| 0.0.134 | 6 / 3 | |
| 0.0.133 | 6 / 3 | |
| 0.0.132 | 6 / 3 | |
| 0.0.131 | 6 / 3 | |
| 0.0.130 | 6 / 3 | |
| 0.0.129 | 6 / 3 | |
| 0.0.128 | 6 / 3 | |
| 0.0.127 | 6 / 3 | |
| 0.0.126 | 6 / 3 | |
| 0.0.125 | 6 / 3 |
v0.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.