@teambit/status
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 hundreds of scoped packages simultaneously; rapid publish is expected behavior. | ai | |
| provenance | no-provenance | AI (provenance): Monorepo package; provenance attestation not enforced for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is stable across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lane-id | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-issues | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-version | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.component-list | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.snap-distance | AI (dependencies): Internal @teambit org sibling package; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@teambit/objects | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for @teambit packages. | ai | |
| phantom-deps | phantom-dep:@teambit/legacy.consumer-component | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for @teambit packages. | ai |
Versions (showing 100 of 218)
| Version | Deps | Published |
|---|---|---|
| 1.0.727 | 23 / 3 | |
| 1.0.726 | 23 / 3 | |
| 1.0.725 | 23 / 3 | |
| 1.0.717 | 23 / 3 | |
| 1.0.716 | 23 / 3 | |
| 1.0.714 | 23 / 3 | |
| 1.0.712 | 23 / 3 | |
| 1.0.704 | 23 / 3 | |
| 1.0.699 | 23 / 3 | |
| 1.0.696 | 23 / 3 | |
| 1.0.695 | 23 / 3 | |
| 1.0.694 | 23 / 3 | |
| 1.0.691 | 23 / 3 | |
| 1.0.689 | 23 / 3 | |
| 1.0.683 | 23 / 3 | |
| 1.0.681 | 23 / 3 | |
| 1.0.678 | 23 / 3 | |
| 1.0.676 | 23 / 3 | |
| 1.0.674 | 23 / 3 | |
| 1.0.668 | 23 / 3 | |
| 1.0.665 | 23 / 3 | |
| 1.0.662 | 23 / 3 | |
| 1.0.660 | 23 / 3 | |
| 1.0.657 | 23 / 3 | |
| 1.0.655 | 23 / 3 | |
| 1.0.652 | 23 / 3 | |
| 1.0.650 | 23 / 3 | |
| 1.0.649 | 23 / 3 | |
| 1.0.646 | 23 / 3 | |
| 1.0.644 | 23 / 3 | |
| 1.0.642 | 23 / 3 | |
| 1.0.641 | 23 / 3 | |
| 1.0.640 | 23 / 3 | |
| 1.0.634 | 23 / 3 | |
| 1.0.631 | 23 / 3 | |
| 1.0.630 | 23 / 3 | |
| 1.0.628 | 23 / 3 | |
| 1.0.626 | 23 / 3 | |
| 1.0.622 | 23 / 3 | |
| 1.0.620 | 23 / 3 | |
| 1.0.617 | 23 / 3 | |
| 1.0.613 | 23 / 3 | |
| 1.0.332 | 15 / 4 | |
| 1.0.331 | 15 / 4 | |
| 1.0.330 | 15 / 4 | |
| 1.0.329 | 15 / 4 | |
| 1.0.328 | 15 / 4 | |
| 1.0.327 | 15 / 4 | |
| 1.0.326 | 15 / 4 | |
| 1.0.325 | 15 / 4 | |
| 1.0.324 | 15 / 4 | |
| 1.0.323 | 15 / 4 | |
| 1.0.322 | 15 / 4 | |
| 1.0.321 | 15 / 4 | |
| 1.0.320 | 15 / 4 | |
| 1.0.319 | 15 / 4 | |
| 1.0.318 | 15 / 4 | |
| 1.0.317 | 15 / 4 | |
| 1.0.316 | 15 / 4 | |
| 1.0.315 | 15 / 4 | |
| 1.0.314 | 15 / 4 | |
| 1.0.313 | 15 / 4 | |
| 1.0.312 | 15 / 4 | |
| 1.0.311 | 15 / 4 | |
| 1.0.310 | 15 / 4 | |
| 1.0.309 | 15 / 4 | |
| 1.0.308 | 15 / 4 | |
| 1.0.307 | 15 / 4 | |
| 1.0.306 | 15 / 4 | |
| 1.0.305 | 15 / 4 | |
| 1.0.304 | 15 / 4 | |
| 1.0.303 | 15 / 4 | |
| 1.0.302 | 15 / 4 | |
| 1.0.301 | 15 / 4 | |
| 1.0.300 | 15 / 4 | |
| 1.0.299 | 15 / 4 | |
| 1.0.298 | 15 / 4 | |
| 1.0.297 | 15 / 4 | |
| 1.0.296 | 15 / 4 | |
| 1.0.295 | 15 / 4 | |
| 1.0.294 | 15 / 4 | |
| 1.0.293 | 15 / 4 | |
| 1.0.292 | 15 / 4 | |
| 1.0.291 | 15 / 4 | |
| 1.0.290 | 15 / 4 | |
| 1.0.289 | 15 / 4 | |
| 1.0.288 | 15 / 4 | |
| 1.0.287 | 15 / 4 | |
| 1.0.286 | 15 / 4 | |
| 1.0.285 | 15 / 4 | |
| 1.0.284 | 15 / 4 | |
| 1.0.283 | 15 / 4 | |
| 1.0.282 | 15 / 4 | |
| 1.0.281 | 15 / 4 | |
| 1.0.280 | 15 / 4 | |
| 1.0.279 | 15 / 4 | |
| 1.0.278 | 15 / 4 | |
| 1.0.277 | 15 / 4 | |
| 1.0.276 | 15 / 4 | |
| 1.0.275 | 15 / 4 |
v1.0.332
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.331
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.