@teambit/mover
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI/CD releasing many packages rapidly; stable pattern across thousands of approved versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.node-modules-linker | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component package; missing description is a cosmetic issue, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Established teambit/bit monorepo predates widespread provenance adoption; absence is expected. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): Sibling @teambit/* package from the same monorepo; unvetted status is a registry coverage gap, not a risk. | ai |
Versions (showing 100 of 312)
| Version | Deps | Published |
|---|---|---|
| 1.0.663 | 12 / 4 | |
| 1.0.662 | 12 / 4 | |
| 1.0.661 | 12 / 4 | |
| 1.0.660 | 12 / 4 | |
| 1.0.659 | 12 / 4 | |
| 1.0.656 | 12 / 4 | |
| 1.0.655 | 12 / 4 | |
| 1.0.654 | 12 / 4 | |
| 1.0.652 | 12 / 4 | |
| 1.0.651 | 12 / 4 | |
| 1.0.650 | 12 / 4 | |
| 1.0.649 | 12 / 4 | |
| 1.0.648 | 12 / 4 | |
| 1.0.645 | 12 / 4 | |
| 1.0.644 | 12 / 4 | |
| 1.0.643 | 12 / 4 | |
| 1.0.642 | 12 / 4 | |
| 1.0.641 | 12 / 4 | |
| 1.0.640 | 12 / 4 | |
| 1.0.638 | 12 / 4 | |
| 1.0.637 | 12 / 4 | |
| 1.0.636 | 12 / 4 | |
| 1.0.635 | 12 / 4 | |
| 1.0.633 | 12 / 4 | |
| 1.0.631 | 12 / 4 | |
| 1.0.630 | 12 / 4 | |
| 1.0.628 | 12 / 4 | |
| 1.0.627 | 12 / 4 | |
| 1.0.625 | 12 / 4 | |
| 1.0.624 | 12 / 4 | |
| 1.0.623 | 12 / 4 | |
| 1.0.621 | 12 / 4 | |
| 1.0.618 | 12 / 4 | |
| 1.0.617 | 12 / 4 | |
| 1.0.616 | 12 / 4 | |
| 1.0.612 | 12 / 4 | |
| 1.0.611 | 12 / 4 | |
| 1.0.610 | 12 / 4 | |
| 1.0.330 | 8 / 5 | |
| 1.0.329 | 8 / 5 | |
| 1.0.328 | 8 / 5 | |
| 1.0.327 | 8 / 5 | |
| 1.0.326 | 8 / 5 | |
| 1.0.325 | 8 / 5 | |
| 1.0.324 | 8 / 5 | |
| 1.0.323 | 8 / 5 | |
| 1.0.322 | 8 / 5 | |
| 1.0.321 | 8 / 5 | |
| 1.0.320 | 8 / 5 | |
| 1.0.319 | 8 / 5 | |
| 1.0.318 | 8 / 5 | |
| 1.0.317 | 8 / 5 | |
| 1.0.316 | 8 / 5 | |
| 1.0.315 | 8 / 5 | |
| 1.0.314 | 8 / 5 | |
| 1.0.313 | 8 / 5 | |
| 1.0.312 | 8 / 5 | |
| 1.0.311 | 8 / 5 | |
| 1.0.310 | 8 / 5 | |
| 1.0.309 | 8 / 5 | |
| 1.0.308 | 8 / 5 | |
| 1.0.307 | 8 / 5 | |
| 1.0.306 | 8 / 5 | |
| 1.0.305 | 8 / 5 | |
| 1.0.304 | 8 / 5 | |
| 1.0.303 | 8 / 5 | |
| 1.0.302 | 8 / 5 | |
| 1.0.301 | 8 / 5 | |
| 1.0.300 | 8 / 5 | |
| 1.0.299 | 8 / 5 | |
| 1.0.298 | 8 / 5 | |
| 1.0.297 | 8 / 5 | |
| 1.0.296 | 8 / 5 | |
| 1.0.295 | 8 / 5 | |
| 1.0.294 | 8 / 5 | |
| 1.0.293 | 8 / 5 | |
| 1.0.292 | 8 / 5 | |
| 1.0.291 | 8 / 5 | |
| 1.0.290 | 8 / 5 | |
| 1.0.289 | 8 / 5 | |
| 1.0.288 | 8 / 5 | |
| 1.0.287 | 8 / 5 | |
| 1.0.286 | 8 / 5 | |
| 1.0.285 | 8 / 5 | |
| 1.0.284 | 8 / 5 | |
| 1.0.283 | 8 / 5 | |
| 1.0.282 | 8 / 5 | |
| 1.0.281 | 8 / 5 | |
| 1.0.280 | 8 / 5 | |
| 1.0.279 | 8 / 5 | |
| 1.0.278 | 8 / 5 | |
| 1.0.277 | 8 / 5 | |
| 1.0.276 | 8 / 5 | |
| 1.0.275 | 8 / 5 | |
| 1.0.274 | 8 / 5 | |
| 1.0.273 | 8 / 5 | |
| 1.0.272 | 8 / 5 | |
| 1.0.271 | 8 / 5 | |
| 1.0.270 | 8 / 5 | |
| 1.0.269 | 8 / 5 |
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.