@just-every/ensemble
LLM provider abstraction layer with unified streaming interface
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Declared dependency used in WebSocket functionality; stable false positive. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dependency used for schema validation; stable false positive. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared dependency used in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Declared dependency used in server functionality; stable false positive. | ai |
Versions (showing 100 of 281)
| Version | Deps | Published |
|---|---|---|
| 0.2.249 | 5 / 14 | |
| 0.2.248 | 5 / 14 | |
| 0.2.247 | 5 / 14 | |
| 0.2.246 | 5 / 14 | |
| 0.2.245 | 5 / 14 | |
| 0.2.244 | 5 / 14 | |
| 0.2.243 | 5 / 14 | |
| 0.2.242 | 5 / 14 | |
| 0.2.241 | 5 / 14 | |
| 0.2.240 | 5 / 14 | |
| 0.2.239 | 5 / 14 | |
| 0.2.238 | 5 / 14 | |
| 0.2.237 | 5 / 14 | |
| 0.2.236 | 5 / 14 | |
| 0.2.235 | 5 / 14 | |
| 0.2.234 | 5 / 14 | |
| 0.2.233 | 5 / 14 | |
| 0.2.232 | 5 / 14 | |
| 0.2.231 | 5 / 14 | |
| 0.2.230 | 5 / 14 | |
| 0.2.229 | 5 / 14 | |
| 0.2.228 | 5 / 14 | |
| 0.2.227 | 5 / 14 | |
| 0.2.226 | 5 / 14 | |
| 0.2.225 | 5 / 14 | |
| 0.2.224 | 5 / 14 | |
| 0.2.223 | 5 / 14 | |
| 0.2.222 | 5 / 14 | |
| 0.2.221 | 5 / 14 | |
| 0.2.220 | 5 / 14 | |
| 0.2.219 | 5 / 14 | |
| 0.2.218 | 5 / 14 | |
| 0.2.217 | 5 / 14 | |
| 0.2.216 | 5 / 14 | |
| 0.2.214 | 5 / 14 | |
| 0.2.213 | 5 / 14 | |
| 0.2.212 | 5 / 14 | |
| 0.2.211 | 5 / 14 | |
| 0.2.210 | 5 / 14 | |
| 0.2.209 | 5 / 14 | |
| 0.2.208 | 5 / 14 | |
| 0.2.207 | 5 / 14 | |
| 0.2.206 | 5 / 14 | |
| 0.2.205 | 5 / 14 | |
| 0.2.204 | 5 / 14 | |
| 0.2.203 | 5 / 14 | |
| 0.2.202 | 5 / 14 | |
| 0.2.201 | 5 / 14 | |
| 0.2.200 | 5 / 14 | |
| 0.2.199 | 5 / 14 | |
| 0.2.198 | 5 / 14 | |
| 0.2.197 | 5 / 14 | |
| 0.2.196 | 5 / 14 | |
| 0.2.195 | 5 / 14 | |
| 0.2.194 | 5 / 14 | |
| 0.2.193 | 5 / 14 | |
| 0.2.192 | 5 / 14 | |
| 0.2.191 | 5 / 14 | |
| 0.2.190 | 5 / 14 | |
| 0.2.189 | 5 / 14 | |
| 0.2.188 | 5 / 14 | |
| 0.2.187 | 5 / 14 | |
| 0.2.186 | 5 / 14 | |
| 0.2.185 | 5 / 14 | |
| 0.2.184 | 5 / 14 | |
| 0.2.183 | 5 / 14 | |
| 0.2.182 | 5 / 14 | |
| 0.2.181 | 5 / 14 | |
| 0.2.180 | 5 / 14 | |
| 0.2.179 | 5 / 14 | |
| 0.2.178 | 5 / 14 | |
| 0.2.177 | 5 / 14 | |
| 0.2.176 | 5 / 14 | |
| 0.2.175 | 5 / 14 | |
| 0.2.174 | 5 / 14 | |
| 0.2.173 | 5 / 14 | |
| 0.2.172 | 5 / 14 | |
| 0.2.171 | 5 / 14 | |
| 0.2.170 | 5 / 14 | |
| 0.2.169 | 5 / 14 | |
| 0.2.168 | 5 / 14 | |
| 0.2.167 | 5 / 14 | |
| 0.2.166 | 5 / 15 | |
| 0.2.165 | 5 / 15 | |
| 0.2.164 | 5 / 15 | |
| 0.2.163 | 5 / 15 | |
| 0.2.162 | 5 / 15 | |
| 0.2.161 | 4 / 15 | |
| 0.2.160 | 4 / 15 | |
| 0.2.159 | 4 / 15 | |
| 0.2.158 | 4 / 15 | |
| 0.2.157 | 4 / 15 | |
| 0.2.156 | 4 / 15 | |
| 0.2.155 | 4 / 15 | |
| 0.2.154 | 4 / 15 | |
| 0.2.153 | 4 / 15 | |
| 0.2.152 | 4 / 15 | |
| 0.2.151 | 4 / 15 | |
| 0.2.150 | 4 / 15 | |
| 0.2.149 | 4 / 15 |
v0.2.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.