@bubblelab/bubble-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chart.js | AI (phantom-deps): chart.js is a peer/config dep for chartjs-node-canvas; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Schema utility likely used indirectly via LangChain integrations. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): TypeScript type package loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@langchain/community | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai |
Versions (showing 100 of 297)
| Version | Deps | Published |
|---|---|---|
| 0.1.324 | 20 / 6 | |
| 0.1.323 | 20 / 6 | |
| 0.1.322 | 20 / 6 | |
| 0.1.321 | 20 / 6 | |
| 0.1.320 | 20 / 6 | |
| 0.1.319 | 20 / 6 | |
| 0.1.318 | 20 / 6 | |
| 0.1.317 | 20 / 6 | |
| 0.1.316 | 20 / 6 | |
| 0.1.314 | 20 / 6 | |
| 0.1.313 | 20 / 6 | |
| 0.1.312 | 20 / 6 | |
| 0.1.311 | 20 / 6 | |
| 0.1.310 | 20 / 6 | |
| 0.1.309 | 20 / 6 | |
| 0.1.308 | 20 / 6 | |
| 0.1.307 | 20 / 6 | |
| 0.1.306 | 20 / 6 | |
| 0.1.305 | 20 / 6 | |
| 0.1.304 | 20 / 6 | |
| 0.1.303 | 20 / 6 | |
| 0.1.302 | 20 / 6 | |
| 0.1.301 | 20 / 6 | |
| 0.1.300 | 20 / 6 | |
| 0.1.299 | 20 / 6 | |
| 0.1.298 | 20 / 6 | |
| 0.1.297 | 20 / 6 | |
| 0.1.296 | 20 / 6 | |
| 0.1.295 | 20 / 6 | |
| 0.1.294 | 20 / 6 | |
| 0.1.293 | 20 / 6 | |
| 0.1.292 | 20 / 6 | |
| 0.1.291 | 20 / 6 | |
| 0.1.289 | 20 / 6 | |
| 0.1.288 | 20 / 6 | |
| 0.1.287 | 20 / 6 | |
| 0.1.286 | 20 / 6 | |
| 0.1.285 | 20 / 6 | |
| 0.1.284 | 20 / 6 | |
| 0.1.283 | 20 / 6 | |
| 0.1.282 | 20 / 6 | |
| 0.1.281 | 20 / 6 | |
| 0.1.280 | 20 / 6 | |
| 0.1.279 | 20 / 6 | |
| 0.1.278 | 20 / 6 | |
| 0.1.277 | 20 / 6 | |
| 0.1.276 | 20 / 6 | |
| 0.1.275 | 20 / 6 | |
| 0.1.273 | 20 / 6 | |
| 0.1.272 | 20 / 6 | |
| 0.1.271 | 20 / 6 | |
| 0.1.270 | 20 / 6 | |
| 0.1.269 | 20 / 6 | |
| 0.1.268 | 20 / 6 | |
| 0.1.267 | 20 / 6 | |
| 0.1.266 | 20 / 6 | |
| 0.1.265 | 20 / 6 | |
| 0.1.263 | 20 / 6 | |
| 0.1.262 | 20 / 6 | |
| 0.1.261 | 20 / 6 | |
| 0.1.255 | 20 / 6 | |
| 0.1.254 | 20 / 6 | |
| 0.1.253 | 20 / 6 | |
| 0.1.252 | 20 / 6 | |
| 0.1.251 | 20 / 6 | |
| 0.1.250 | 20 / 6 | |
| 0.1.249 | 20 / 6 | |
| 0.1.248 | 20 / 6 | |
| 0.1.247 | 20 / 6 | |
| 0.1.246 | 20 / 6 | |
| 0.1.245 | 20 / 6 | |
| 0.1.244 | 20 / 6 | |
| 0.1.243 | 20 / 6 | |
| 0.1.242 | 20 / 6 | |
| 0.1.241 | 20 / 6 | |
| 0.1.240 | 20 / 6 | |
| 0.1.239 | 20 / 6 | |
| 0.1.238 | 20 / 6 | |
| 0.1.237 | 20 / 6 | |
| 0.1.236 | 20 / 6 | |
| 0.1.235 | 20 / 6 | |
| 0.1.234 | 20 / 6 | |
| 0.1.233 | 20 / 6 | |
| 0.1.232 | 20 / 6 | |
| 0.1.231 | 20 / 6 | |
| 0.1.230 | 20 / 6 | |
| 0.1.229 | 20 / 6 | |
| 0.1.228 | 20 / 6 | |
| 0.1.227 | 20 / 6 | |
| 0.1.226 | 20 / 6 | |
| 0.1.225 | 20 / 6 | |
| 0.1.224 | 20 / 6 | |
| 0.1.223 | 20 / 6 | |
| 0.1.222 | 20 / 6 | |
| 0.1.221 | 20 / 6 | |
| 0.1.220 | 20 / 6 | |
| 0.1.219 | 20 / 6 | |
| 0.1.218 | 20 / 6 | |
| 0.1.217 | 20 / 6 | |
| 0.1.216 | 20 / 6 |
v0.1.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.