@teambit/merge-lanes
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Internal same-org Bit monorepo dependency, not unvetted third-party code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @teambit package within same monorepo/org. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.feature-toggle | AI (dependencies): Same @teambit org scope; consistent with this package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.cli.prompts | AI (dependencies): Same @teambit org scope; consistent with this package's established dependency pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI/CD releasing many packages rapidly; consistent pattern across 2437+ versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.snap-distance | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.get-basic-log | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.modules.merge-helper | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/lane-id | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Bit ecosystem packages routinely omit npm descriptions; not a malware indicator here. | ai | |
| phantom-deps | phantom-dep:@teambit/component.snap-distance | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Bit's modular monorepo structure. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes thousands of packages without Sigstore provenance; consistent across the ecosystem. | ai |
Versions (showing 100 of 401)
| Version | Deps | Published |
|---|---|---|
| 1.0.637 | 32 / 4 | |
| 1.0.516 | 32 / 8 | |
| 1.0.386 | 26 / 10 | |
| 1.0.330 | 22 / 10 | |
| 1.0.329 | 22 / 10 | |
| 1.0.328 | 22 / 10 | |
| 1.0.327 | 22 / 10 | |
| 1.0.326 | 22 / 10 | |
| 1.0.325 | 22 / 10 | |
| 1.0.324 | 22 / 10 | |
| 1.0.323 | 22 / 10 | |
| 1.0.322 | 22 / 10 | |
| 1.0.321 | 22 / 10 | |
| 1.0.320 | 22 / 10 | |
| 1.0.319 | 22 / 10 | |
| 1.0.318 | 22 / 10 | |
| 1.0.317 | 22 / 10 | |
| 1.0.316 | 22 / 10 | |
| 1.0.315 | 22 / 10 | |
| 1.0.314 | 22 / 10 | |
| 1.0.313 | 22 / 10 | |
| 1.0.312 | 22 / 10 | |
| 1.0.311 | 22 / 10 | |
| 1.0.310 | 22 / 10 | |
| 1.0.309 | 22 / 10 | |
| 1.0.308 | 22 / 10 | |
| 1.0.307 | 22 / 10 | |
| 1.0.306 | 22 / 10 | |
| 1.0.305 | 22 / 10 | |
| 1.0.304 | 22 / 10 | |
| 1.0.303 | 22 / 10 | |
| 1.0.302 | 22 / 10 | |
| 1.0.301 | 22 / 10 | |
| 1.0.300 | 22 / 10 | |
| 1.0.299 | 22 / 10 | |
| 1.0.298 | 22 / 10 | |
| 1.0.297 | 22 / 10 | |
| 1.0.296 | 22 / 10 | |
| 1.0.295 | 22 / 10 | |
| 1.0.294 | 22 / 10 | |
| 1.0.293 | 22 / 10 | |
| 1.0.292 | 22 / 10 | |
| 1.0.291 | 22 / 10 | |
| 1.0.290 | 22 / 10 | |
| 1.0.289 | 22 / 10 | |
| 1.0.288 | 22 / 10 | |
| 1.0.287 | 22 / 10 | |
| 1.0.286 | 22 / 10 | |
| 1.0.285 | 22 / 10 | |
| 1.0.284 | 22 / 10 | |
| 1.0.283 | 22 / 10 | |
| 1.0.282 | 22 / 10 | |
| 1.0.281 | 22 / 10 | |
| 1.0.280 | 22 / 10 | |
| 1.0.279 | 22 / 10 | |
| 1.0.278 | 22 / 10 | |
| 1.0.277 | 22 / 10 | |
| 1.0.276 | 22 / 10 | |
| 1.0.275 | 22 / 10 | |
| 1.0.274 | 22 / 10 | |
| 1.0.273 | 22 / 10 | |
| 1.0.272 | 22 / 10 | |
| 1.0.271 | 22 / 10 | |
| 1.0.270 | 22 / 10 | |
| 1.0.269 | 22 / 10 | |
| 1.0.268 | 22 / 10 | |
| 1.0.267 | 22 / 10 | |
| 1.0.266 | 22 / 10 | |
| 1.0.265 | 22 / 10 | |
| 1.0.264 | 22 / 10 | |
| 1.0.263 | 22 / 10 | |
| 1.0.262 | 22 / 10 | |
| 1.0.261 | 22 / 10 | |
| 1.0.260 | 22 / 10 | |
| 1.0.259 | 22 / 10 | |
| 1.0.258 | 22 / 10 | |
| 1.0.257 | 22 / 10 | |
| 1.0.256 | 22 / 10 | |
| 1.0.255 | 22 / 10 | |
| 1.0.254 | 22 / 10 | |
| 1.0.253 | 22 / 10 | |
| 1.0.252 | 22 / 10 | |
| 1.0.251 | 22 / 10 | |
| 1.0.250 | 22 / 10 | |
| 1.0.249 | 22 / 10 | |
| 1.0.248 | 22 / 10 | |
| 1.0.247 | 22 / 10 | |
| 1.0.246 | 22 / 10 | |
| 1.0.245 | 22 / 10 | |
| 1.0.244 | 22 / 10 | |
| 1.0.243 | 22 / 10 | |
| 1.0.242 | 22 / 10 | |
| 1.0.241 | 22 / 10 | |
| 1.0.240 | 22 / 5 | |
| 1.0.239 | 22 / 5 | |
| 1.0.238 | 22 / 5 | |
| 1.0.237 | 22 / 5 | |
| 1.0.235 | 22 / 5 | |
| 1.0.234 | 22 / 5 | |
| 1.0.233 | 22 / 5 |
v1.0.516
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.386
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.330
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.329
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.328
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.326
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.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.
v1.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.
v1.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.
v1.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.
v1.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.
v1.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.
v1.0.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.0.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.297
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.296
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.255
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.254
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.253
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.252
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.249
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.238
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.235
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.234
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.233
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.